<div dir="ltr"><div>Hi<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, May 3, 2021 at 2:16 PM Hyeonggon Yoo <<a href="mailto:42.hyeyoo@gmail.com">42.hyeyoo@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div dir="auto">Greg, and Valdis Thank you so much! It helped a lot!</div><div dir="auto"><br></div><div dir="auto">I thought there would be a way to do it because of high resolution.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">2021년 5월 3일 (월) 오후 8:13, Valdis Klētnieks <<a href="mailto:valdis.kletnieks@vt.edu" target="_blank">valdis.kletnieks@vt.edu</a>>님이 작성:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Mon, 03 May 2021 00:56:17 +0900, Hyeonggon Yoo said:<br>
<br>
> I mean, is there an API that guarantees high precision (non architecture<br>
> dependent way)<br>
<br>
How do you guarantee high precision if you're on hardware that doesn't<br>
provide a high precision/resolution timer?<br></blockquote></div></blockquote><div><br></div><div>If you don't have any hardware support, the Linux kernel can't magically count faster than its system tick. ^^<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
</blockquote></div>
_______________________________________________<br>
Kernelnewbies mailing list<br>
<a href="mailto:Kernelnewbies@kernelnewbies.org" target="_blank">Kernelnewbies@kernelnewbies.org</a><br>
<a href="https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies" rel="noreferrer" target="_blank">https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies</a><br>
</blockquote></div></div>