From: Janosch Frank <frankja@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: thuth@redhat.com, david@redhat.com, cohuck@redhat.com,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
mihajlov@linux.ibm.com
Subject: [PATCH 0/3] s390x: Increase architectural compliance
Date: Fri, 29 Nov 2019 09:20:22 -0500 [thread overview]
Message-ID: <20191129142025.21453-1-frankja@linux.ibm.com> (raw)
On a diag 308 subcode 0 and 1 we need to load the whole reset PSW and
not just the address.
On a cpu reset normal, we need to clear local cpus. Unfortunately we
need a new API for that, since KVM only exposes one of the three
resets.
Patches are also in my cleanup branch.
Janosch Frank (3):
s390x: Properly fetch and test the short psw on diag308 subc 0/1
Sync reset
s390x: protvirt: Add new VCPU reset functions
linux-headers/linux/kvm.h | 7 +++++++
target/s390x/cpu.c | 26 ++++++++++++++++++++++----
target/s390x/cpu.h | 1 +
target/s390x/kvm-stub.c | 10 +++++++++-
target/s390x/kvm.c | 38 ++++++++++++++++++++++++++++++++------
target/s390x/kvm_s390x.h | 4 +++-
6 files changed, 74 insertions(+), 12 deletions(-)
--
2.20.1
next reply other threads:[~2019-11-29 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 14:20 Janosch Frank [this message]
2019-11-29 14:20 ` [PATCH 1/3] s390x: Properly fetch and test the short psw on diag308 subc 0/1 Janosch Frank
2019-12-02 9:13 ` Cornelia Huck
2019-12-18 16:55 ` Cornelia Huck
2019-11-29 14:20 ` [PATCH 2/3] Sync reset Janosch Frank
2019-11-29 14:20 ` [PATCH 3/3] s390x: protvirt: Add new VCPU reset functions Janosch Frank
2019-11-29 14:24 ` David Hildenbrand
2019-11-29 14:34 ` Janosch Frank
2019-11-29 14:36 ` David Hildenbrand
2019-12-02 8:57 ` [PATCH 0/3] s390x: Increase architectural compliance Cornelia Huck
2019-12-02 8:59 ` Janosch Frank
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=20191129142025.21453-1-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mihajlov@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.