[Top][All Lists]

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

Re: [Bug 1858461] Re: Please refactor linux-user/mips/cpu_loop.c

From: Peter Maydell
Subject: Re: [Bug 1858461] Re: Please refactor linux-user/mips/cpu_loop.c
Date: Wed, 8 Jan 2020 17:56:17 +0000

On Wed, 8 Jan 2020 at 17:06, puchuu <address@hidden> wrote:
> I think about the following development flow:
> 1. Kernel updates and maintains "tbl".
> 2. Qemu developer wants to implement new syscall (like clone3) in 
> "linux-user/syscall.c".
> 3. Developer clones new kernel into some directory and runs generators.
> 4. All syscall related stuff will be updated immediately.

That seems like quite a lot of effort, given that we don't really
have to update the set of syscall number #defines very often.
At the moment it's just "somebody submits a patch which
updates the list of #defines every so often". (And if you want
to actually implement a new syscall then the the actual
implementation is the bulk of the work anyhow.)

In particular if you really want to proceed down the path of
suggesting scripts for doing the update then I think we would
want something that works for all our architectures, not just MIPS.

-- PMM

reply via email to

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