unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Linux: Use 32-bit vDSO for clock_gettime, gettimeofday, time (bug 28071)
Date: Sat, 10 Jul 2021 20:54:10 +0200	[thread overview]
Message-ID: <878s2ef19p.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <ed69a8d8-ee2a-8b14-840d-0fd9f12e387e@linaro.org> (Adhemerval Zanella's message of "Sat, 10 Jul 2021 15:22:20 -0300")

* Adhemerval Zanella:

> This does not fix the issue for __ASSUME_TIME64_SYSCALLS where it still uses
> INLINE_SYSCALL_CALL which might clobber the errno, besides adding another
> ifdef code path (which I really want to avoid).  Instead I think we need to 
> open-coded the INLINE_VSYSCALL macro and replace all INLINE_SYSCALL_CALL 
> with INTERNAL_SYSCALL_CALLS:

But for __ASSUME_TIME64_SYSCALLS, clock_gettime64 will not fail.

What am I missing?  Is the issue that INLINE_VSYSCALL may set ENOSYS
artificially?

Thanks,
Florian


  reply	other threads:[~2021-07-10 18:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-10 17:15 [PATCH] Linux: Use 32-bit vDSO for clock_gettime, gettimeofday, time (bug 28071) Florian Weimer via Libc-alpha
2021-07-10 18:22 ` Adhemerval Zanella via Libc-alpha
2021-07-10 18:54   ` Florian Weimer via Libc-alpha [this message]
2021-07-10 19:57     ` Adhemerval Zanella via Libc-alpha
2021-07-10 20:00       ` Florian Weimer via Libc-alpha
2021-07-10 20:03         ` Adhemerval Zanella via Libc-alpha
2021-07-10 20:30         ` Adhemerval Zanella via Libc-alpha
2021-07-12 10:40           ` Florian Weimer via Libc-alpha
2021-07-12 11:55             ` Adhemerval Zanella via Libc-alpha
2021-07-12 13:15               ` Florian Weimer via Libc-alpha
2021-07-12 14:20                 ` Adhemerval Zanella via Libc-alpha
2021-07-12 14:29                   ` Florian Weimer via Libc-alpha
2021-07-12 15:46                     ` Adhemerval Zanella via Libc-alpha
2021-07-12 17:55                       ` Florian Weimer via Libc-alpha
2021-07-12 18:00                         ` Adhemerval Zanella via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878s2ef19p.fsf@oldenburg.str.redhat.com \
    --to=libc-alpha@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.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).