[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181120180741.iu6bcjprjxeqllem@treble>
Date: Tue, 20 Nov 2018 12:07:41 -0600
From: Josh Poimboeuf <jpoimboe@...hat.com>
To: Andy Lutomirski <luto@...nel.org>
Cc: Florian Weimer <fweimer@...hat.com>, X86 ML <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
Peter Zijlstra <peterz@...radead.org>,
Tycho Andersen <tycho@...ho.ws>,
Daniel Colascione <dancol@...gle.com>,
Carlos O'Donell <carlos@...hat.com>,
Rich Felker <dalias@...c.org>,
Adhemerval Zanella <adhemerval.zanella@...aro.org>
Subject: Re: Cleaning up numbering for new x86 syscalls?
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@...hat.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
Powered by blists - more mailing lists