From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "Carlos O'Donell" <carlos@redhat.com>,
Florian Weimer <fweimer@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Boqun Feng <boqun.feng@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>,
libc-alpha <libc-alpha@sourceware.org>
Subject: Re: Restartable Sequences system call merged into Linux
Date: Wed, 13 Jun 2018 11:48:00 -0000 [thread overview]
Message-ID: <20180613114811.GC4342@osiris> (raw)
In-Reply-To: <1084280721.10859.1528746558696.JavaMail.zimbra@efficios.com>
On Mon, Jun 11, 2018 at 03:49:18PM -0400, Mathieu Desnoyers wrote:
> Hi!
>
> Good news! The restartable sequences (rseq) system call is now merged into the master
> branch of the Linux kernel within the 4.18 merge window:
>
> https://github.com/torvalds/linux/commit/d82991a8688ad128b46db1b42d5d84396487a508
>
> It would be important to discuss how we should proceed to integrate the library part
> of rseq (see tools/testing/selftests/rseq/rseq*.{ch}) into glibc, or if it should
> live in a standalone project.
Is there any documentation available of what is the exact semantics of the
functions that have to be implemented for additional architectures?
I could look at rseq-skip.h and e.g. rseq-x86.h and try to figure out what
would be the correct implementation for s390. But having that somewhere
written down, e.g. as comments in one of the implementations, would be very
helpful.
next prev parent reply other threads:[~2018-06-13 11:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 19:49 Mathieu Desnoyers
2018-06-11 19:55 ` Florian Weimer
2018-06-11 20:04 ` Mathieu Desnoyers
2018-06-12 13:11 ` Florian Weimer
2018-06-12 16:31 ` Mathieu Desnoyers
2018-06-13 8:23 ` Florian Weimer
2018-06-14 12:28 ` Pavel Machek
2018-06-14 13:02 ` Mathieu Desnoyers
2018-06-14 13:26 ` Pavel Machek
2018-06-14 13:32 ` Florian Weimer
2018-06-14 13:46 ` Mathieu Desnoyers
2018-06-15 5:10 ` Florian Weimer
2018-06-15 17:44 ` Mathieu Desnoyers
2018-06-14 13:38 ` Mathieu Desnoyers
2018-06-14 13:50 ` Pavel Machek
2018-06-14 14:01 ` Florian Weimer
2018-06-14 14:36 ` Mathieu Desnoyers
2018-06-14 14:41 ` Florian Weimer
2018-06-14 15:09 ` Mathieu Desnoyers
2018-06-15 5:09 ` Florian Weimer
2018-06-15 17:50 ` Mathieu Desnoyers
2018-06-15 5:07 ` Florian Weimer
2018-06-13 11:48 ` Heiko Carstens [this message]
2018-06-13 16:14 ` Mathieu Desnoyers
2018-06-13 19:53 ` Mathieu Desnoyers
2018-07-11 16:03 ` Stefan Liebler
2018-07-11 16:23 ` Adhemerval Zanella
2018-07-11 17:19 ` Florian Weimer
2018-07-11 17:42 ` Adhemerval Zanella
2018-07-11 17:45 ` Florian Weimer
2018-07-11 17:59 ` Adhemerval Zanella
2018-07-12 8:08 ` Stefan Liebler
2018-07-11 19:05 ` Carlos O'Donell
2018-07-12 8:10 ` Szabolcs Nagy
2018-07-13 13:22 ` Stefan Liebler
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=20180613114811.GC4342@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=boqun.feng@gmail.com \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).