3f8258c1 | 11-Apr-2018 |
Laurent Vivier <laurent@vivier.eu> |
linux-user: move i386/x86_64 cpu loop to i386 directory
No code change, only move code from main.c to i386/cpu_loop.c.
Include i386/cpu_loop.c in x86_64/cpu_loop.c to avoid to duplicate code.
Sign
linux-user: move i386/x86_64 cpu loop to i386 directory
No code change, only move code from main.c to i386/cpu_loop.c.
Include i386/cpu_loop.c in x86_64/cpu_loop.c to avoid to duplicate code.
Signed-off-by: Laurent Vivier <laurent@vivier.eu> Reviewed-by: Richard Henderson <richard.henderson@linaro.org> Message-Id: <20180411185651.21351-3-laurent@vivier.eu>
show more ...
|
93a92d3b | 15-Feb-2016 |
Riku Voipio <riku.voipio@linaro.org> |
linux-user: correct timerfd_create syscall numbers
x86, m68k, ppc, sh4 and sparc failed to enable timerfd, because they didn't have timerfd_create system call defined. Instead QEMU defined timerfd s
linux-user: correct timerfd_create syscall numbers
x86, m68k, ppc, sh4 and sparc failed to enable timerfd, because they didn't have timerfd_create system call defined. Instead QEMU defined timerfd syscall. Checking with kernel sources, it appears kernel developers reused timerfd syscall number with timerfd_create, presumably since no userspace called the old syscall number.
Reported-by: Laurent Vivier <laurent@vivier.eu> Reviewed-by: Laurent Vivier <laurent@vivier.eu> Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
show more ...
|