From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757430AbaCFAQx (ORCPT ); Wed, 5 Mar 2014 19:16:53 -0500 Received: from terminus.zytor.com ([198.137.202.10]:38615 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754326AbaCFAQw (ORCPT ); Wed, 5 Mar 2014 19:16:52 -0500 Message-ID: <5317BE63.1000600@zytor.com> Date: Wed, 05 Mar 2014 16:16:35 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Andy Lutomirski CC: "linux-kernel@vger.kernel.org" , linux-arch , libseccomp-discuss@lists.sourceforge.net Subject: Re: Making a universal list of syscalls? References: <53162927.4040401@zytor.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/05/2014 04:13 PM, Andy Lutomirski wrote: > > I think that SYSCALLS.def won't work as is -- SYSCALLS.def > references unistd, which ought to be autogenerated from the syscalls > list. But a somewhat less magical variant should work. > Well, that is because unistd.h is one of the very few things the kernel actually *does* export (containing system call numbers, and *usually* is enough to detect presence/absence of a certain system call, which is actually all you need in the vast majority of cases.) -hpa