From: riku.voipio@linaro.org
To: qemu-devel@nongnu.org
Cc: Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PULL 21/24] linux-user: Provide safe_syscall for arm
Date: Fri, 24 Jun 2016 12:53:16 +0300 [thread overview]
Message-ID: <f0bcaed799b5c3ff7980c341af90d2f244fb91de.1466760944.git.riku.voipio@linaro.org> (raw)
In-Reply-To: <cover.1466760944.git.riku.voipio@linaro.org>
From: Richard Henderson <rth@twiddle.net>
Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
Signed-off-by: Richard Henderson <rth@twiddle.net>
Signed-off-by: Riku Voipio <riku.voipio@linaro.org>
---
linux-user/host/arm/hostdep.h | 23 +++++++++
linux-user/host/arm/safe-syscall.inc.S | 90 ++++++++++++++++++++++++++++++++++
2 files changed, 113 insertions(+)
create mode 100644 linux-user/host/arm/safe-syscall.inc.S
diff --git a/linux-user/host/arm/hostdep.h b/linux-user/host/arm/hostdep.h
index 7609bf5..8e1ff2f 100644
--- a/linux-user/host/arm/hostdep.h
+++ b/linux-user/host/arm/hostdep.h
@@ -12,4 +12,27 @@
#ifndef QEMU_HOSTDEP_H
#define QEMU_HOSTDEP_H
+/* We have a safe-syscall.inc.S */
+#define HAVE_SAFE_SYSCALL
+
+#ifndef __ASSEMBLER__
+
+/* These are defined by the safe-syscall.inc.S file */
+extern char safe_syscall_start[];
+extern char safe_syscall_end[];
+
+/* Adjust the signal context to rewind out of safe-syscall if we're in it */
+static inline void rewind_if_in_safe_syscall(void *puc)
+{
+ struct ucontext *uc = puc;
+ unsigned long *pcreg = &uc->uc_mcontext.arm_pc;
+
+ if (*pcreg > (uintptr_t)safe_syscall_start
+ && *pcreg < (uintptr_t)safe_syscall_end) {
+ *pcreg = (uintptr_t)safe_syscall_start;
+ }
+}
+
+#endif /* __ASSEMBLER__ */
+
#endif
diff --git a/linux-user/host/arm/safe-syscall.inc.S b/linux-user/host/arm/safe-syscall.inc.S
new file mode 100644
index 0000000..88c4958
--- /dev/null
+++ b/linux-user/host/arm/safe-syscall.inc.S
@@ -0,0 +1,90 @@
+/*
+ * safe-syscall.inc.S : host-specific assembly fragment
+ * to handle signals occurring at the same time as system calls.
+ * This is intended to be included by linux-user/safe-syscall.S
+ *
+ * Written by Richard Henderson <rth@twiddle.net>
+ * Copyright (C) 2016 Red Hat, Inc.
+ *
+ * This work is licensed under the terms of the GNU GPL, version 2 or later.
+ * See the COPYING file in the top-level directory.
+ */
+
+ .global safe_syscall_base
+ .global safe_syscall_start
+ .global safe_syscall_end
+ .type safe_syscall_base, %function
+
+ .cfi_sections .debug_frame
+
+ .text
+ .syntax unified
+ .arm
+ .align 2
+
+ /* This is the entry point for making a system call. The calling
+ * convention here is that of a C varargs function with the
+ * first argument an 'int *' to the signal_pending flag, the
+ * second one the system call number (as a 'long'), and all further
+ * arguments being syscall arguments (also 'long').
+ * We return a long which is the syscall's return value, which
+ * may be negative-errno on failure. Conversion to the
+ * -1-and-errno-set convention is done by the calling wrapper.
+ */
+safe_syscall_base:
+ .fnstart
+ .cfi_startproc
+ mov r12, sp /* save entry stack */
+ push { r4, r5, r6, r7, r8, lr }
+ .save { r4, r5, r6, r7, r8, lr }
+ .cfi_adjust_cfa_offset 24
+ .cfi_rel_offset r4, 0
+ .cfi_rel_offset r5, 4
+ .cfi_rel_offset r6, 8
+ .cfi_rel_offset r7, 12
+ .cfi_rel_offset r8, 16
+ .cfi_rel_offset lr, 20
+
+ /* The syscall calling convention isn't the same as the C one:
+ * we enter with r0 == *signal_pending
+ * r1 == syscall number
+ * r2, r3, [sp+0] ... [sp+12] == syscall arguments
+ * and return the result in r0
+ * and the syscall instruction needs
+ * r7 == syscall number
+ * r0 ... r6 == syscall arguments
+ * and returns the result in r0
+ * Shuffle everything around appropriately.
+ * Note the 16 bytes that we pushed to save registers.
+ */
+ mov r8, r0 /* copy signal_pending */
+ mov r7, r1 /* syscall number */
+ mov r0, r2 /* syscall args */
+ mov r1, r3
+ ldm r12, { r2, r3, r4, r5, r6 }
+
+ /* This next sequence of code works in conjunction with the
+ * rewind_if_safe_syscall_function(). If a signal is taken
+ * and the interrupted PC is anywhere between 'safe_syscall_start'
+ * and 'safe_syscall_end' then we rewind it to 'safe_syscall_start'.
+ * The code sequence must therefore be able to cope with this, and
+ * the syscall instruction must be the final one in the sequence.
+ */
+safe_syscall_start:
+ /* if signal_pending is non-zero, don't do the call */
+ ldr r12, [r8] /* signal_pending */
+ tst r12, r12
+ bne 1f
+ swi 0
+safe_syscall_end:
+ /* code path for having successfully executed the syscall */
+ pop { r4, r5, r6, r7, r8, pc }
+
+1:
+ /* code path when we didn't execute the syscall */
+ ldr r0, =-TARGET_ERESTARTSYS
+ pop { r4, r5, r6, r7, r8, pc }
+ .fnend
+ .cfi_endproc
+
+ .size safe_syscall_base, .-safe_syscall_base
--
2.1.4
next prev parent reply other threads:[~2016-06-24 9:53 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-24 9:52 [Qemu-devel] [PULL 00/24] linux-user changes riku.voipio
2016-06-24 9:52 ` [Qemu-devel] [PULL 01/24] linux-user: Avoid possible misalignment in host_to_target_siginfo() riku.voipio
2016-06-24 9:52 ` [Qemu-devel] [PULL 02/24] linux-user: Use __get_user() and __put_user() to handle structs in do_fcntl() riku.voipio
2016-06-24 9:52 ` [Qemu-devel] [PULL 03/24] linux-user: Use safe_syscall wrapper for fcntl riku.voipio
2016-06-24 9:52 ` [Qemu-devel] [PULL 04/24] linux-user: Don't use sigfillset() on uc->uc_sigmask riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 05/24] configure: Don't override ARCH=unknown if enabling TCI riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 06/24] configure: Don't allow user-only targets for unknown CPU architectures riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 07/24] user-exec: Delete now-unused hppa and m68k cpu_signal_handler() code riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 08/24] user-exec: Remove unused code for OSX hosts riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 09/24] linux-user: Create a hostdep.h for each host architecture riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 10/24] linux-user: Fix wrong type used for argument to rt_sigqueueinfo riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 11/24] linux-user: Support F_GETPIPE_SZ and F_SETPIPE_SZ fcntls riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 12/24] linux-user: add socketcall() strace riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 13/24] linux-user: add socket() strace riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 14/24] linux-user: fix clone() strace riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 15/24] linux-user: update get_thread_area/set_thread_area strace riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 16/24] linux-user: add missing return in netlink switch statement riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 17/24] linux-user: fd_trans_host_to_target_data() must process only received data riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 18/24] linux-user: don't swap NLMSG_DATA() fields riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 19/24] linux-user: fix x86_64 safe_syscall riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 20/24] linux-user: Provide safe_syscall for i386 riku.voipio
2016-06-24 9:53 ` riku.voipio [this message]
2016-06-24 9:53 ` [Qemu-devel] [PULL 22/24] linux-user: Provide safe_syscall for aarch64 riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 23/24] linux-user: Provide safe_syscall for s390x riku.voipio
2016-06-24 9:53 ` [Qemu-devel] [PULL 24/24] linux-user: Provide safe_syscall for ppc64 riku.voipio
2016-06-24 13:36 ` [Qemu-devel] [PULL 00/24] linux-user changes Peter Maydell
2016-06-26 10:34 ` Riku Voipio
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=f0bcaed799b5c3ff7980c341af90d2f244fb91de.1466760944.git.riku.voipio@linaro.org \
--to=riku.voipio@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).