From: "Edgecombe, Rick P" <rick.p.edgecombe@intel.com>
To: "Lutomirski, Andy" <luto@kernel.org>,
"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>,
"peterz@infradead.org" <peterz@infradead.org>,
"hpa@zytor.com" <hpa@zytor.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"Mehta, Sohil" <sohil.mehta@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "broonie@kernel.org" <broonie@kernel.org>
Subject: Re: [PATCH] selftests/x86: Update map_shadow_stack syscall nr
Date: Fri, 1 Sep 2023 22:51:23 +0000 [thread overview]
Message-ID: <339cd90a9b77706bd65b6d45f49edf009a9d46a0.camel@intel.com> (raw)
In-Reply-To: <148522e4-a4ec-a35b-df25-e04eeb5f51c4@intel.com>
On Fri, 2023-09-01 at 15:19 -0700, Sohil Mehta wrote:
> My suggestion is originating from the belief that at somepoint the
> community decided that all *new* system call numbers would be the
> consistent across architectures (except alpha). So that would mean
> syscall number 453 has to be reserved on others even if it is an
> x86-only syscall.
>
> If we don't do this, and let say a generic sys_foo comes along which
> uses the next available syscall number 453 on other archs, it would
> lead
> to an inconsistency because 453 it is already used up on x86.
>
> My memory of this is a bit hazy from my implementation of User
> Interrupts more than a couple of years back. Also, I couldn't find
> any
> handy documentation to support my belief. I'll try to dig more.
Putting reservations in sounds like a good idea in any case. I take it
you would like to send the patch? Otherwise let me know.
next prev parent reply other threads:[~2023-09-01 22:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 18:16 Rick Edgecombe
2023-09-01 19:33 ` Sohil Mehta
2023-09-01 20:35 ` Edgecombe, Rick P
2023-09-01 22:19 ` Sohil Mehta
2023-09-01 22:51 ` Edgecombe, Rick P [this message]
2023-09-02 0:12 ` Sohil Mehta
2023-09-01 21:39 ` [tip: x86/urgent] " tip-bot2 for Rick Edgecombe
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=339cd90a9b77706bd65b6d45f49edf009a9d46a0.camel@intel.com \
--to=rick.p.edgecombe@intel.com \
--cc=bp@alien8.de \
--cc=broonie@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®