aboutsummaryrefslogtreecommitdiff
path: root/linux-user/m68k
diff options
context:
space:
mode:
authorRiku Voipio <riku.voipio@linaro.org>2016-02-15 15:38:40 +0200
committerRiku Voipio <riku.voipio@linaro.org>2016-02-23 21:25:10 +0200
commit93a92d3bd649cd315db47b9fb5dcb6af657cc22c (patch)
tree25d4eb8348939c6aa6b30b0ca630be014be1f256 /linux-user/m68k
parent13756fb008728e0c316d6b183c8740e030b1ad74 (diff)
downloadqemu-93a92d3bd649cd315db47b9fb5dcb6af657cc22c.zip
qemu-93a92d3bd649cd315db47b9fb5dcb6af657cc22c.tar.gz
qemu-93a92d3bd649cd315db47b9fb5dcb6af657cc22c.tar.bz2
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>
Diffstat (limited to 'linux-user/m68k')
-rw-r--r--linux-user/m68k/syscall_nr.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/linux-user/m68k/syscall_nr.h b/linux-user/m68k/syscall_nr.h
index a2daba0..4b50fb2 100644
--- a/linux-user/m68k/syscall_nr.h
+++ b/linux-user/m68k/syscall_nr.h
@@ -317,7 +317,7 @@
#define TARGET_NR_epoll_pwait 315
#define TARGET_NR_utimensat 316
#define TARGET_NR_signalfd 317
-#define TARGET_NR_timerfd 318
+#define TARGET_NR_timerfd_create 318
#define TARGET_NR_eventfd 319
#define TARGET_NR_fallocate 320
#define TARGET_NR_timerfd_settime 321