From: Max Filippov <jcmvbkbc@gmail.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Max Filippov <jcmvbkbc@gmail.com>,
Riku Voipio <riku.voipio@iki.fi>,
Laurent Vivier <laurent@vivier.eu>
Subject: [Qemu-devel] [PULL 0/8] xtensa-specific and generic fixes for linux-user
Date: Mon, 2 Apr 2018 10:13:46 -0700 [thread overview]
Message-ID: <20180402171354.27706-1-jcmvbkbc@gmail.com> (raw)
Hi Peter,
please pull the following batch of linux-user fixes for 2.12.
The following changes since commit dfe732fb68ef9195517f4f380a477d58a054edc1:
Merge remote-tracking branch 'remotes/jnsnow/tags/ide-pull-request' into staging (2018-03-27 16:25:12 +0100)
are available in the git repository at:
git://github.com/OSLL/qemu-xtensa.git tags/20180402-xtensa
for you to fetch changes up to 64a563dd8dd6ca2661d96a2e4b69f0a5465cab94:
target/xtensa: linux-user: fix fadvise64 call (2018-04-02 04:15:35 -0700)
----------------------------------------------------------------
xtensa-specific fixes for linux-user:
- fix flushing registers for signal processing in call8 and call12 frames;
- fix PC value for restarted syscalls;
- fix sysv IPC structures;
- fix fadvise64 syscall;
generic fixes for linux-user:
- fix QEMU assertion in multithreaded application by calling cpu_copy
under clone_lock;
- fix mq_getsetattr implementation;
- fix error propagation in clock_gettime;
- implement clock_settime.
----------------------------------------------------------------
Max Filippov (8):
target/xtensa: fix flush_window_regs
target/xtensa: linux-user: rewind pc for restarted syscall
linux-user: call cpu_copy under clone_lock
linux-user: fix mq_getsetattr implementation
target/xtensa: linux-user: fix sysv IPC structures
linux-user: fix error propagation in clock_gettime
linux-user: implement clock_settime
target/xtensa: linux-user: fix fadvise64 call
linux-user/main.c | 3 +++
linux-user/signal.c | 55 +++++++++++++++++---------------------
linux-user/syscall.c | 36 +++++++++++++++++--------
linux-user/xtensa/target_structs.h | 37 ++++++++++++++++++++-----
4 files changed, 82 insertions(+), 49 deletions(-)
--
Thanks.
-- Max
next reply other threads:[~2018-04-02 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-02 17:13 Max Filippov [this message]
2018-04-02 17:13 ` [Qemu-devel] [PULL 1/8] target/xtensa: fix flush_window_regs Max Filippov
2018-04-02 17:13 ` [Qemu-devel] [PULL 2/8] target/xtensa: linux-user: rewind pc for restarted syscall Max Filippov
2018-04-02 17:13 ` [Qemu-devel] [PULL 3/8] linux-user: call cpu_copy under clone_lock Max Filippov
2018-04-02 17:13 ` [Qemu-devel] [PULL 4/8] linux-user: fix mq_getsetattr implementation Max Filippov
2018-04-02 17:13 ` [Qemu-devel] [PULL 5/8] target/xtensa: linux-user: fix sysv IPC structures Max Filippov
2018-04-02 17:13 ` [Qemu-devel] [PULL 6/8] linux-user: fix error propagation in clock_gettime Max Filippov
2018-04-02 17:13 ` [Qemu-devel] [PULL 7/8] linux-user: implement clock_settime Max Filippov
2018-04-02 17:13 ` [Qemu-devel] [PULL 8/8] target/xtensa: linux-user: fix fadvise64 call Max Filippov
2018-04-03 22:23 ` [Qemu-devel] [PULL 0/8] xtensa-specific and generic fixes for linux-user 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=20180402171354.27706-1-jcmvbkbc@gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=laurent@vivier.eu \
--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).