Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1193855 > unrolled thread
| Started by | David Drysdale <drysdale@google.com> |
|---|---|
| First post | 2015-07-28 10:10 +0200 |
| Last post | 2015-07-28 10:10 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
[PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs David Drysdale <drysdale@google.com> - 2015-07-28 10:10 +0200
| From | David Drysdale <drysdale@google.com> |
|---|---|
| Date | 2015-07-28 10:10 +0200 |
| Subject | [PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs |
| Message-ID | <pR87w-3jY-31@gated-at.bofh.it> |
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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web