From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: Eduardo Habkost <ehabkost@redhat.com>,
Riku Voipio <riku.voipio@iki.fi>,
Laurent Vivier <laurent@vivier.eu>,
Aleksandar Markovic <amarkovic@wavecomp.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Aleksandar Rikalo <aleksandar.rikalo@rt-rk.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Richard Henderson <rth@twiddle.net>
Subject: [PULL 7/9] linux-user: x86_64: Update syscall numbers to kernel 5.5 level
Date: Mon, 17 Feb 2020 10:30:29 +0100 [thread overview]
Message-ID: <20200217093031.678348-8-laurent@vivier.eu> (raw)
In-Reply-To: <20200217093031.678348-1-laurent@vivier.eu>
From: Aleksandar Markovic <amarkovic@wavecomp.com>
Update x86_64 syscall numbers based on Linux kernel v5.5.
CC: Paolo Bonzini <pbonzini@redhat.com>
CC: Richard Henderson <rth@twiddle.net>
CC: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Aleksandar Markovic <amarkovic@wavecomp.com>
Reviewed-by: Laurent Vivier <laurent@vivier.eu>
Message-Id: <1581596954-2305-8-git-send-email-aleksandar.markovic@rt-rk.com>
Signed-off-by: Laurent Vivier <laurent@vivier.eu>
---
linux-user/x86_64/syscall_nr.h | 24 ++++++++++++++++++++++++
1 file changed, 24 insertions(+)
diff --git a/linux-user/x86_64/syscall_nr.h b/linux-user/x86_64/syscall_nr.h
index 9b6981e74cea..e5d14eca223d 100644
--- a/linux-user/x86_64/syscall_nr.h
+++ b/linux-user/x86_64/syscall_nr.h
@@ -328,5 +328,29 @@
#define TARGET_NR_membarrier 324
#define TARGET_NR_mlock2 325
#define TARGET_NR_copy_file_range 326
+#define TARGET_NR_preadv2 327
+#define TARGET_NR_pwritev2 328
+#define TARGET_NR_pkey_mprotect 329
+#define TARGET_NR_pkey_alloc 330
+#define TARGET_NR_pkey_free 331
+#define TARGET_NR_statx 332
+#define TARGET_NR_io_pgetevents 333
+#define TARGET_NR_rseq 334
+/*
+ * don't use numbers 387 through 423, add new calls after the last
+ * 'common' entry
+ */
+#define TARGET_NR_pidfd_send_signal 424
+#define TARGET_NR_io_uring_setup 425
+#define TARGET_NR_io_uring_enter 426
+#define TARGET_NR_io_uring_register 427
+#define TARGET_NR_open_tree 428
+#define TARGET_NR_move_mount 429
+#define TARGET_NR_fsopen 430
+#define TARGET_NR_fsconfig 431
+#define TARGET_NR_fsmount 432
+#define TARGET_NR_fspick 433
+#define TARGET_NR_pidfd_open 434
+#define TARGET_NR_clone3 435
#endif
--
2.24.1
next prev parent reply other threads:[~2020-02-17 9:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 9:30 [PULL 0/9] Linux user for 5.0 patches Laurent Vivier
2020-02-17 9:30 ` [PULL 1/9] linux-user: alpha: Update syscall numbers to kernel 5.5 level Laurent Vivier
2020-02-17 9:30 ` [PULL 2/9] linux-user: arm: " Laurent Vivier
2020-02-17 9:30 ` [PULL 3/9] linux-user: m68k: " Laurent Vivier
2020-02-17 9:30 ` [PULL 4/9] linux-user: microblaze: " Laurent Vivier
2020-02-17 9:30 ` [PULL 5/9] linux-user: mips: " Laurent Vivier
2020-02-17 9:30 ` [PULL 6/9] linux-user: sh4: " Laurent Vivier
2020-02-17 9:30 ` Laurent Vivier [this message]
2020-02-17 9:30 ` [PULL 8/9] linux-user: xtensa: " Laurent Vivier
2020-02-17 9:30 ` [PULL 9/9] linux-user: xtensa: Remove unused constant TARGET_NR_syscall_count Laurent Vivier
2020-02-17 13:17 ` [PULL 0/9] Linux user for 5.0 patches Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200217093031.678348-8-laurent@vivier.eu \
--to=laurent@vivier.eu \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
--cc=rth@twiddle.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).