From: Joseph Myers <joseph@codesourcery.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: carlos <carlos@redhat.com>, Florian Weimer <fweimer@redhat.com>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
libc-alpha <libc-alpha@sourceware.org>,
Thomas Gleixner <tglx@linutronix.de>, Ben Maurer <bmaurer@fb.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
Will Deacon <will.deacon@arm.com>,
Dave Watson <davejwatson@fb.com>, Paul Turner <pjt@google.com>,
Rich Felker <dalias@libc.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-api <linux-api@vger.kernel.org>
Subject: Re: [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at C startup and thread creation (v6)
Date: Wed, 30 Jan 2019 21:10:07 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1901302104360.16754@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1832200535.4162.1548871426959.JavaMail.zimbra@efficios.com>
On Wed, 30 Jan 2019, Mathieu Desnoyers wrote:
> #if defined (__NR_rseq) && !defined (RSEQ_SIG)
> # error "UAPI headers support rseq system call, but glibc does not define RSEQ_SIG."
> #endif
>
> Would that take care of your concerns ?
That would of course need appropriate conditionals based on the most
recent kernel version for which a given glibc version has been updated, so
that using new kernel headers with an existing glibc release does not make
the build fail (cf. the test of syscall-names.list). And being able to
write such a test only solves one half of the problem - it needs to be
easy to determine what value to put in that header in glibc for an
architecture that's newly gained support in the kernel, *without* needing
any architecture expertise.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-01-30 21:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 21:35 [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at C startup and thread creation (v6) Mathieu Desnoyers
2019-01-21 21:35 ` [RFC PATCH glibc 2/4] glibc: sched_getcpu(): use rseq cpu_id TLS on Linux Mathieu Desnoyers
2019-01-21 21:35 ` [RFC PATCH glibc 3/4] support record failure: allow use from constructor Mathieu Desnoyers
2019-01-21 21:35 ` [RFC PATCH glibc 4/4] rseq registration tests (v2) Mathieu Desnoyers
2019-01-29 16:57 ` [RFC PATCH glibc 1/4] glibc: Perform rseq(2) registration at C startup and thread creation (v6) Mathieu Desnoyers
2019-01-29 21:56 ` Joseph Myers
2019-01-30 1:39 ` Mathieu Desnoyers
2019-01-30 2:40 ` Joseph Myers
2019-01-30 18:03 ` Mathieu Desnoyers
2019-01-30 18:30 ` Zack Weinberg
2019-01-30 18:51 ` Florian Weimer
2019-01-30 20:38 ` Mathieu Desnoyers
2019-01-30 21:10 ` Joseph Myers [this message]
2019-01-31 16:37 ` Mathieu Desnoyers
2019-01-31 16:53 ` Mathieu Desnoyers
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=alpine.DEB.2.21.1901302104360.16754@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bmaurer@fb.com \
--cc=boqun.feng@gmail.com \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=davejwatson@fb.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=szabolcs.nagy@arm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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).