From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-devel@nongnu.org
Cc: Riku Voipio <riku.voipio@iki.fi>,
Richard Henderson <rth@twiddle.net>,
"Andrei E. Warkentin" <andrey.warkentin@gmail.com>,
patches@linaro.org
Subject: [Qemu-devel] [PATCH for-2.0? 0/2] fix bugs involving linux-user signal handling
Date: Thu, 3 Apr 2014 17:45:06 +0100 [thread overview]
Message-ID: <1396543508-12280-1-git-send-email-peter.maydell@linaro.org> (raw)
This patch series fixes bugs reported by Andrei Warkentin involving
signal handling in linux-user mode. The first is Andrei's first patch
(though I have tweaked the commit message a little). The second
patch is aimed at fixing the locking bug that Andrei noted, in
a somewhat simpler way than his patches use.
The test cases Andrei provided both pass with these patches.
(The tb_lock is a completely ill-thought-out idea anyway; maybe
one day we'll actually sort out how multiple linux-user threads
should interact with the TCG data structures. But for now this
fixes an obvious bug.)
Andrei Warkentin (1):
page_check_range: don't bail out early after unprotecting page
Peter Maydell (1):
cpu-exec: Unlock tb_lock if we longjmp out of code generation
cpu-exec.c | 7 +++++++
translate-all.c | 1 -
2 files changed, 7 insertions(+), 1 deletion(-)
--
1.9.0
next reply other threads:[~2014-04-03 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 16:45 Peter Maydell [this message]
2014-04-03 16:45 ` [Qemu-devel] [PATCH for-2.0? 1/2] page_check_range: don't bail out early after unprotecting page Peter Maydell
2014-04-03 18:26 ` Richard Henderson
2014-04-03 16:45 ` [Qemu-devel] [PATCH for-2.0? 2/2] cpu-exec: Unlock tb_lock if we longjmp out of code generation Peter Maydell
2014-04-03 16:51 ` Richard Henderson
2014-04-03 16:53 ` Peter Maydell
2014-04-03 19:38 ` Andrei E. Warkentin
2014-04-03 23:24 ` 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=1396543508-12280-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=andrey.warkentin@gmail.com \
--cc=patches@linaro.org \
--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).