From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Rafael Eduardo Ruviaro Christ
<rafaeleduardoruviaro.christ@asml.com>,
'GNU C Library' <libc-alpha@sourceware.org>
Subject: Re: aarch64 lacks HP_TIMING support in glibc
Date: Fri, 2 Jul 2021 10:53:10 -0300 [thread overview]
Message-ID: <06b1464a-cefe-0e57-30e4-634c5b03c2d1@linaro.org> (raw)
In-Reply-To: <VE1PR08MB55994A005C0B5B6DDAD2CBC4831F9@VE1PR08MB5599.eurprd08.prod.outlook.com>
On 02/07/2021 10:13, Wilco Dijkstra via Libc-alpha wrote:
> You could propose a RFC to improve the clock_getres implementation and see
> what people say. It might help if you have use cases where knowing the exact
> resolution is essential.
>
I really prefer if we avoid trying to hack this on userspace and let the
kernel handle it instead, specially if requires a arch-specific implementation.
I think it is really unlikely that we would get a better resolution in
userspace that kernel can't provide more efficiently.
next prev parent reply other threads:[~2021-07-02 13:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 11:43 Wilco Dijkstra
2021-06-23 13:26 ` Adhemerval Zanella
2021-06-23 15:19 ` Wilco Dijkstra
2021-06-28 15:49 ` Rafael Eduardo Ruviaro Christ
2021-06-28 19:25 ` Wilco Dijkstra
2021-06-30 13:27 ` Rafael Eduardo Ruviaro Christ
2021-07-02 13:13 ` Wilco Dijkstra
2021-07-02 13:53 ` Adhemerval Zanella [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-22 18:29 Rafael Eduardo Ruviaro Christ
2021-06-22 18:38 ` Andrew Pinski
2021-06-22 18:57 ` Adhemerval Zanella
2021-06-22 19:27 ` Andreas Schwab
2021-06-22 19:53 ` Adhemerval Zanella
2021-06-22 20:18 ` Andreas Schwab
2021-06-22 20:22 ` Adhemerval Zanella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06b1464a-cefe-0e57-30e4-634c5b03c2d1@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=Wilco.Dijkstra@arm.com \
--cc=libc-alpha@sourceware.org \
--cc=rafaeleduardoruviaro.christ@asml.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).