Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932323AbbG1IJA (ORCPT ); Tue, 28 Jul 2015 04:09:00 -0400 Received: from mail-wi0-f172.google.com ([209.85.212.172]:32978 "EHLO mail-wi0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932191AbbG1IFs (ORCPT ); Tue, 28 Jul 2015 04:05:48 -0400 From: David Drysdale To: x86@kernel.org, Thomas Gleixner , Ingo Molnar , Andy Lutomirski , "H. Peter Anvin" Cc: Michael Kerrisk , Kees Cook , Paul Moore , Eric Paris , linux-api@vger.kernel.org, linux-kernel@vger.kernel.org, David Drysdale Subject: [PATCH RFC 0/1] UAPI,x86: export syscall numbers for all x86 archs Date: Tue, 28 Jul 2015 09:05:30 +0100 Message-Id: <1438070731-17764-1-git-send-email-drysdale@google.com> X-Mailer: git-send-email 2.5.0.rc2.392.g76e840b Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1259 Lines: 29 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/