[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/9] linux-user: Update syscall numbers to kernel 5.5 level
From: |
Stafford Horne |
Subject: |
Re: [PATCH 0/9] linux-user: Update syscall numbers to kernel 5.5 level |
Date: |
Thu, 6 Feb 2020 06:29:01 +0900 |
User-agent: |
Mutt/1.11.4 (2019-03-13) |
On Tue, Feb 04, 2020 at 01:07:29PM +0100, Aleksandar Markovic wrote:
> From: Aleksandar Markovic <address@hidden>
>
> This series also doesn't cover following files (since I can't find
> corresponding kernel code - and I am also asking corresponding
> target maintainers or Lauren to update them, if possible, before
> our 5.0 release):
OpenRISC is in the kernel under arch/openrisc and the syscall numbers we
user are just like other architectures, it's in:
linux/arch/openrisc/include/uapi/asm/unistd.h
This then includes the generic numbers:
linux/include/uapi/asm-generic/unistd.h
There are other architectures in the kernel, like arm64, risvc, nios2 using the
generic syscall numbers.
Should QEMU also have linux-user/generic/syscall_nr.h that mirrors the generic
file in linux? This way this could be maintained in just one place.
> - linux-user/cris/cpu_loop.c
> - linux-user/hppa/syscall_nr.h
> - linux-user/openrisc/syscall_nr.h
> - linux-user/tilegx/syscall_nr.h
>
> CC: Edgar E. Iglesias <address@hidden>
> CC: Richard Henderson <address@hidden>
> CC: Stafford Horne <address@hidden>
>
> Again, I don't plan (I am really running out of time resources) to
> work in a significant way on this issue any more, and I am asking
> you guys other maintainers to help finish updating syscall numbers
> before QEMU 5.0 release.
I actually have a patch to add syscall numbers for openrisc which I am using to
test our new glibc port right now. I will clean if up and submit for review.
It looks like for 5.0 we would need to get changes in by March 23:
https://wiki.qemu.org/Planning/5.0
I'll try to aim to get my change up for review soon then.
-Stafford
- [PATCH 7/9] linux-user: x86_64: Update syscall numbers to kernel 5.5 level, (continued)
- [PATCH 7/9] linux-user: x86_64: Update syscall numbers to kernel 5.5 level, Aleksandar Markovic, 2020/02/04
- [PATCH 8/9] linux-user: xtensa: Update syscall numbers to kernel 5.5 level, Aleksandar Markovic, 2020/02/04
- [PATCH 5/9] linux-user: mips: Update syscall numbers to kernel 5.5 level, Aleksandar Markovic, 2020/02/04
- [PATCH 9/9] linux-user: xtensa: Remove unused constant TARGET_NR_syscall_count, Aleksandar Markovic, 2020/02/04
- [PATCH 1/9] linux-user: alpha: Update syscall numbers to kernel 5.5 level, Aleksandar Markovic, 2020/02/04
- [PATCH 6/9] linux-user: sh4: Update syscall numbers to kernel 5.5 level, Aleksandar Markovic, 2020/02/04
- Re: [PATCH 0/9] linux-user: Update syscall numbers to kernel 5.5 level, Aleksandar Markovic, 2020/02/04
- Re: [PATCH 0/9] linux-user: Update syscall numbers to kernel 5.5 level,
Stafford Horne <=
- Re: [PATCH 0/9] linux-user: Update syscall numbers to kernel 5.5 level, Laurent Vivier, 2020/02/12