From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Andy Lutomirski <luto@kernel.org>
Cc: Florian Weimer <fweimer@redhat.com>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
Peter Zijlstra <peterz@infradead.org>,
Tycho Andersen <tycho@tycho.ws>,
Daniel Colascione <dancol@google.com>,
Carlos O'Donell <carlos@redhat.com>,
Rich Felker <dalias@libc.org>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: Cleaning up numbering for new x86 syscalls?
Date: Tue, 20 Nov 2018 12:07:41 -0600 [thread overview]
Message-ID: <20181120180741.iu6bcjprjxeqllem@treble> (raw)
In-Reply-To: <CALCETrVJO-GSbQCGNJS_F1ZswG15aWOdX7onWFYgTVhh97WbWg@mail.gmail.com>
On Tue, Nov 20, 2018 at 07:23:09AM -0800, Andy Lutomirski wrote:
> On Tue, Nov 20, 2018 at 1:03 AM Florian Weimer <fweimer@redhat.com> wrote:
> >
> > * Andy Lutomirski:
> >
> > > 5. Adjust the scripts so that we only have to wire up new syscalls
> > > once. They'll have a nr above 1024, and they'll have the same nr on
> > > all x86 variants.
> >
> > Is there a sufficiently sized gap on all other architectures as well?
> > The restriction to the x86 variants seems arbitrary to me.
> >
>
> Fair point. We have this shiny "generic" syscall list. Maybe we can
> get x86 synced up with it for new syscalls.
I heard this discussed at Plumbers. There was a proposal to use the
same syscall numbers across architectures. Also, when adding new
generic syscalls, they want all arches to be wired up at the same time.
https://linuxplumbersconf.org/event/2/contributions/149/attachments/129/161/Ideas_to_improve_glibc_and_Kernel_interaction.pdf
Adding Adhemerval to CC.
--
Josh
next prev parent reply other threads:[~2018-11-20 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 0:22 Cleaning up numbering for new x86 syscalls? Andy Lutomirski
2018-11-20 7:33 ` Ingo Molnar
2018-11-20 23:04 ` Bernd Petrovitsch
2018-11-30 23:25 ` Maciej W. Rozycki
2018-11-20 9:03 ` Florian Weimer
2018-11-20 15:23 ` Andy Lutomirski
2018-11-20 18:07 ` Josh Poimboeuf [this message]
2018-11-21 17:23 ` Arnd Bergmann
2018-11-20 16:48 ` Tycho Andersen
2018-11-21 17:14 ` Arnd Bergmann
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=20181120180741.iu6bcjprjxeqllem@treble \
--to=jpoimboe@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=bp@alien8.de \
--cc=carlos@redhat.com \
--cc=dalias@libc.org \
--cc=dancol@google.com \
--cc=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=tycho@tycho.ws \
--cc=x86@kernel.org \
/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