From: Christian Borntraeger <borntraeger@de.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Alexander Graf <agraf@suse.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Anthony Liguori <anthony@codemonkey.ws>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Richard Henderson <rth@twiddle.net>
Subject: [Qemu-devel] [PATCH 0/5] s390x/kvm: additional fixes and cleanup
Date: Wed, 26 Feb 2014 12:38:23 +0100 [thread overview]
Message-ID: <1393414708-37739-1-git-send-email-borntraeger@de.ibm.com> (raw)
Folks,
here are 5 additional patches for s390x/kvm that I want to push for 2.0.
Frank Blaschka (1):
s390x/kvm: Rework priv instruction handlers
Thomas Huth (4):
s390x/cpu: Use ioctl to reset state in the kernel
s390x/kvm: Rework SIGP INITIAL CPU RESET handler
s390x/kvm: Add missing SIGP CPU RESET order
s390x/ipl: Fix crash of ELF images with arbitrary entry points
hw/s390x/ipl.c | 21 ++++---
target-s390x/cpu.c | 9 +++
target-s390x/kvm.c | 173 ++++++++++++++++++++++++++++++-----------------------
3 files changed, 120 insertions(+), 83 deletions(-)
--
1.8.4.2
next reply other threads:[~2014-02-26 11:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 11:38 Christian Borntraeger [this message]
2014-02-26 11:38 ` [Qemu-devel] [PATCH 1/5] s390x/cpu: Use ioctl to reset state in the kernel Christian Borntraeger
2014-02-26 11:38 ` [Qemu-devel] [PATCH 2/5] s390x/kvm: Rework SIGP INITIAL CPU RESET handler Christian Borntraeger
2014-02-26 11:38 ` [Qemu-devel] [PATCH 3/5] s390x/kvm: Add missing SIGP CPU RESET order Christian Borntraeger
2014-02-26 11:38 ` [Qemu-devel] [PATCH 4/5] s390x/kvm: Rework priv instruction handlers Christian Borntraeger
2014-02-26 11:38 ` [Qemu-devel] [PATCH 5/5] s390x/ipl: Fix crash of ELF images with arbitrary entry points Christian Borntraeger
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=1393414708-37739-1-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=anthony@codemonkey.ws \
--cc=cornelia.huck@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=peter.maydell@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).