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 v4 0/2] s390x: Improvements to SIGP handling [QEMU]
Date: Fri, 19 Nov 2021 22:43:25 +0100 [thread overview]
Message-ID: <20211119214327.2367026-1-farman@linux.ibm.com> (raw)
Here is an update to the SIGP handling series, to correspond to
version 4 of the KVM series [1].
This should be very similar to v3, but there is only one IOCTL
and it accepts a payload describing the operation.
Unfortunately, I lost track of David's suggested improvement [2]
and have not incorporated nor tested any of it. Next time!
[1] https://lore.kernel.org/all/20211119213707.2363945-1-farman@linux.ibm.com/
[2] https://lore.kernel.org/r/13499d9f-652b-ea75-4ad7-32a347297a55@redhat.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/
v3: https://lore.kernel.org/r/20211110204528.1378524-1-farman@linux.ibm.com/
Eric Farman (2):
Temporary linux-headers update
s390x: Implement the USER_BUSY capability
linux-headers/linux/kvm.h | 16 +++++++++++++++
target/s390x/cpu-sysemu.c | 15 ++++++++++++++
target/s390x/cpu.c | 1 +
target/s390x/cpu.h | 8 ++++++++
target/s390x/kvm/kvm.c | 38 ++++++++++++++++++++++++++++++++++++
target/s390x/kvm/kvm_s390x.h | 2 ++
target/s390x/sigp.c | 19 +++++++++++++++++-
7 files changed, 98 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2021-11-19 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 21:43 Eric Farman [this message]
2021-11-19 21:43 ` [RFC PATCH v4 1/2] Temporary linux-headers update Eric Farman
2021-11-19 21:43 ` [RFC PATCH v4 2/2] s390x: Implement the USER_BUSY capability 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=20211119214327.2367026-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 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.