From: Eric Farman <farman@linux.ibm.com>
To: Halil Pasic <pasic@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Thomas Huth <thuth@redhat.com>,
David Hildenbrand <david@redhat.com>
Cc: Eric Farman <farman@linux.ibm.com>,
qemu-s390x@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel@nongnu.org
Subject: [RFC PATCH v3 0/2] s390x: Improvements to SIGP handling [QEMU]
Date: Wed, 10 Nov 2021 21:45:26 +0100 [thread overview]
Message-ID: <20211110204528.1378524-1-farman@linux.ibm.com> (raw)
Here is an update to the SIGP handling series, to correspond to
version 3 of the KVM series [1].
The main changes here from v2 are the simplified use of
s390_cpu_reset_sigp_busy() throughout the SIGP handlers,
a new invocation of it from s390_cpu_reset(), and the
implementation of the "set sigp busy" IOCTL.
[1] https://lore.kernel.org/r/20211110203322.1374925-1-farman@linux.ibm.com/
Previous RFCs:
v1: https://lore.kernel.org/r/20211008203811.1980478-1-farman@linux.ibm.com/
v2: https://lore.kernel.org/r/20211102201122.3188108-1-farman@linux.ibm.com/
Eric Farman (2):
Temporary linux-headers update
s390x: Implement the USER_SIGP_BUSY capability
linux-headers/linux/kvm.h | 5 +++++
target/s390x/cpu-sysemu.c | 15 +++++++++++++++
target/s390x/cpu.c | 1 +
target/s390x/cpu.h | 8 ++++++++
target/s390x/kvm/kvm.c | 16 ++++++++++++++++
target/s390x/kvm/kvm_s390x.h | 2 ++
target/s390x/sigp.c | 19 ++++++++++++++++++-
7 files changed, 65 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2021-11-10 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 20:45 Eric Farman [this message]
2021-11-10 20:45 ` [RFC PATCH v3 1/2] Temporary linux-headers update Eric Farman
2021-11-10 20:45 ` [RFC PATCH v3 2/2] s390x: Implement the USER_SIGP_BUSY capability Eric Farman
2021-11-11 9:01 ` David Hildenbrand
2021-11-19 21:12 ` Eric Farman
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=20211110204528.1378524-1-farman@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.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 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).