linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Drysdale <drysdale@google.com>
To: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	Andy Lutomirski <luto@amacapital.net>,
	"H. Peter Anvin" <hpa@zytor.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
	Kees Cook <keescook@chromium.org>,
	Paul Moore <paul@paul-moore.com>, Eric Paris <eparis@redhat.com>,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	David Drysdale <drysdale@google.com>
Subject: [PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs
Date: Tue, 28 Jul 2015 09:05:30 +0100	[thread overview]
Message-ID: <1438070731-17764-1-git-send-email-drysdale@google.com> (raw)

A while ago I was trying to build a seccomp-bpf filter program that would
survive a change of x86 architecture.  This was complicated for all sorts of
reasons, but one of the problems was that the different syscall numbers aren't
all available at the same time -- hence this patch.

Naming-wise, Andy Lutomirski has indicated he'd prefer the prefixes to be
__NR_x86_64_, __NR_x86_64_x32_ and __NR_i386_; however, for the latter two
sets of numbers there are existing headers that use different prefixes
(__NR_x32_ and __NR_ia32_), so altering those would involve a change and/or an
additional set of definitions.  For the new constants I've left in my
original suggestion (__NR_amd64_) for the time being.

What are folks' thoughts about the preferred naming for these?


David Drysdale (1):
  UAPI,x86: export syscall numbers for all x86 archs

 arch/x86/entry/syscalls/Makefile | 11 ++++++++---
 arch/x86/include/uapi/asm/Kbuild |  3 +++
 2 files changed, 11 insertions(+), 3 deletions(-)

--
2.4.3.573.g4eafbef

             reply	other threads:[~2015-07-28  8:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  8:05 David Drysdale [this message]
2015-07-28  8:05 ` [PATCH RFC 1/1] UAPI,x86: export syscall numbers for all x86 archs David Drysdale
     [not found] ` <1438070731-17764-1-git-send-email-drysdale-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
2015-07-28 12:20   ` [PATCH RFC 0/1] " Paul Moore
2015-07-28 15:32     ` David Drysdale
     [not found]       ` <CAHse=S8dN+e6nhSrf=hVLsfGyrR191mrxj_wc_OauqNtUXxSCg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-07-28 15:52         ` Paul Moore

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=1438070731-17764-1-git-send-email-drysdale@google.com \
    --to=drysdale@google.com \
    --cc=eparis@redhat.com \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=mtk.manpages@gmail.com \
    --cc=paul@paul-moore.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;
as well as URLs for NNTP newsgroup(s).