qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 00/20] linux-user: generate syscall_nr.sh


From: Laurent Vivier
Subject: Re: [PATCH v2 00/20] linux-user: generate syscall_nr.sh
Date: Fri, 21 Feb 2020 15:37:36 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1

Le 21/02/2020 à 14:56, Peter Maydell a écrit :
> On Fri, 21 Feb 2020 at 13:45, Peter Maydell <address@hidden> wrote:
>>
>> On Wed, 19 Feb 2020 at 22:07, Laurent Vivier <address@hidden> wrote:
>>>
>>> This series copies the files syscall.tbl from linux v5.5 and generates
>>> the file syscall_nr.h from them.
>>>
>>> This is done for all the QEMU targets that have a syscall.tbl
>>> in the linux source tree: mips, mips64, i386, x86_64, sparc, s390x,
>>> ppc, arm, microblaze, sh4, xtensa, m68k, hppa and alpha.
>>>
>>> tilegx and cris are depecrated in linux (tilegx has no maintainer in QEMU)
>>>
>>> aarch64, nios2, openrisc and riscv have no syscall.tbl in linux.
>>
>> Is it the case that all our architectures either:
>>  (1) have a syscall.tbl
>>  (2) are using the asm-generic common numbering system ?
> 
> I think that for asm-generic we should be able to generate
> the syscall_nr.h by suitably defining a __SYSCALL macro
> before #including linux-headers/asm-whatever/unistd.h --
> They basically define syscall numbers like this:
> #define __NR_setxattr 5
> __SYSCALL(__NR_setxattr, sys_setxattr)
> 
> so a C program that just did the autogeneration has the
> info it needs.

Thank you for the hint. I will have a look.

Thanks,
Laurent




reply via email to

[Prev in Thread] Current Thread [Next in Thread]