From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Cc: riku.voipio@iki.fi, peter.maydell@linaro.org
Subject: [Qemu-devel] [PATCH 0/6] linux-user: safe_syscall updates
Date: Mon, 13 Jun 2016 14:45:20 -0700 [thread overview]
Message-ID: <1465854326-19160-1-git-send-email-rth@twiddle.net> (raw)
We added support for x86_64 in 4d330cee37a2; this adds support
for 5 more hosts. Also, tweak the signal_pending test for x86_64.
r~
Richard Henderson (6):
linux-user: fix x86_64 safe_syscall
linux-user: Provide safe_syscall for i386
linux-user: Provide safe_syscall for arm
linux-user: Provide safe_syscall for aarch64
linux-user: Provide safe_syscall for s390x
linux-user: Provide safe_syscall for ppc64
linux-user/host/aarch64/hostdep.h | 34 +++++++++
linux-user/host/aarch64/safe-syscall.inc.S | 72 +++++++++++++++++++
linux-user/host/arm/hostdep.h | 34 +++++++++
linux-user/host/arm/safe-syscall.inc.S | 86 ++++++++++++++++++++++
linux-user/host/i386/hostdep.h | 34 +++++++++
linux-user/host/i386/safe-syscall.inc.S | 110 +++++++++++++++++++++++++++++
linux-user/host/ppc64/hostdep.h | 34 +++++++++
linux-user/host/ppc64/safe-syscall.inc.S | 87 +++++++++++++++++++++++
linux-user/host/s390x/hostdep.h | 34 +++++++++
linux-user/host/s390x/safe-syscall.inc.S | 87 +++++++++++++++++++++++
linux-user/host/x86_64/safe-syscall.inc.S | 6 +-
11 files changed, 615 insertions(+), 3 deletions(-)
create mode 100644 linux-user/host/aarch64/hostdep.h
create mode 100644 linux-user/host/aarch64/safe-syscall.inc.S
create mode 100644 linux-user/host/arm/hostdep.h
create mode 100644 linux-user/host/arm/safe-syscall.inc.S
create mode 100644 linux-user/host/i386/hostdep.h
create mode 100644 linux-user/host/i386/safe-syscall.inc.S
create mode 100644 linux-user/host/ppc64/hostdep.h
create mode 100644 linux-user/host/ppc64/safe-syscall.inc.S
create mode 100644 linux-user/host/s390x/hostdep.h
create mode 100644 linux-user/host/s390x/safe-syscall.inc.S
--
2.5.5
next reply other threads:[~2016-06-13 21:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 21:45 Richard Henderson [this message]
2016-06-13 21:45 ` [Qemu-devel] [PATCH 1/6] linux-user: fix x86_64 safe_syscall Richard Henderson
2016-06-14 11:58 ` Peter Maydell
2016-06-21 19:26 ` Riku Voipio
2016-06-13 21:45 ` [Qemu-devel] [PATCH 2/6] linux-user: Provide safe_syscall for i386 Richard Henderson
2016-06-14 11:58 ` Peter Maydell
2016-06-14 15:47 ` Richard Henderson
2016-06-13 21:45 ` [Qemu-devel] [PATCH 3/6] linux-user: Provide safe_syscall for arm Richard Henderson
2016-06-14 12:04 ` Peter Maydell
2016-06-14 15:53 ` Richard Henderson
2016-06-13 21:45 ` [Qemu-devel] [PATCH 4/6] linux-user: Provide safe_syscall for aarch64 Richard Henderson
2016-06-13 22:04 ` Peter Maydell
2016-06-13 22:21 ` Richard Henderson
2016-06-13 22:28 ` Peter Maydell
2016-06-13 22:31 ` Peter Maydell
2016-06-13 22:38 ` Richard Henderson
2016-06-13 22:40 ` Peter Maydell
2016-06-13 21:45 ` [Qemu-devel] [PATCH 5/6] linux-user: Provide safe_syscall for s390x Richard Henderson
2016-06-13 21:45 ` [Qemu-devel] [PATCH 6/6] linux-user: Provide safe_syscall for ppc64 Richard Henderson
2016-06-13 22:23 ` Peter Maydell
2016-06-13 21:53 ` [Qemu-devel] [PATCH 0/6] linux-user: safe_syscall updates Peter Maydell
2016-06-13 22:09 ` Peter Maydell
2016-06-21 19:08 ` Riku Voipio
2016-06-21 19:49 ` 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=1465854326-19160-1-git-send-email-rth@twiddle.net \
--to=rth@twiddle.net \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=riku.voipio@iki.fi \
/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).