All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Cc: Eric Farman <farman@linux.ibm.com>,
	qemu-s390x@nongnu.org,
	Richard Henderson <richard.henderson@linaro.org>,
	qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>
Subject: [RFC PATCH v2 0/2] s390x: Improvements to SIGP handling [QEMU]
Date: Tue,  2 Nov 2021 21:11:20 +0100	[thread overview]
Message-ID: <20211102201122.3188108-1-farman@linux.ibm.com> (raw)

Here is an update to the SIGP handling I brought up a few
weeks ago [1]. It doesn't share anything with v1, as one of
the patches has already been pulled to master [2] and the
other is now dropped in favor of this direction.

Here, we take advantage of a new KVM ioctl [3] to indicate
when userspace has completed processing a particular SIGP
order, based on David's suggestion [4]. This code resets
the "busy" situation for every order, regardless of whether
the Principles of Operation dictates whether the order
would mark the vcpu busy.

It's not as graceful as I'd like, but it does what I expect
it to. Maybe some more refactoring on this side would help
matters. Thoughts?

[1] https://lore.kernel.org/r/20211008203811.1980478-1-farman@linux.ibm.com/
[2] https://lore.kernel.org/r/20211015091622.1302433-1-thuth@redhat.com/
[3] https://lore.kernel.org/r/20211102194652.2685098-1-farman@linux.ibm.com/
[4] https://lore.kernel.org/r/3e3b38d1-b338-0211-04ab-91f913c1f557@redhat.com/

Eric Farman (2):
  Temporary linux-headers update
  s390x: Implement the USER_SIGP_BUSY capability

 linux-headers/linux/kvm.h    |  4 ++++
 target/s390x/cpu-sysemu.c    |  7 +++++++
 target/s390x/cpu.h           |  4 ++++
 target/s390x/kvm/kvm.c       |  9 ++++++++
 target/s390x/kvm/kvm_s390x.h |  1 +
 target/s390x/sigp.c          | 40 ++++++++++++++++++++++++++++++++++++
 6 files changed, 65 insertions(+)

-- 
2.25.1



             reply	other threads:[~2021-11-02 20:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-02 20:11 Eric Farman [this message]
2021-11-02 20:11 ` [RFC PATCH v2 1/2] Temporary linux-headers update Eric Farman
2021-11-02 20:11 ` [RFC PATCH v2 2/2] s390x: Implement the USER_SIGP_BUSY capability Eric Farman
2021-11-04  8:23   ` David Hildenbrand
2021-11-04 14:55     ` Eric Farman
2021-11-04 15:08       ` David Hildenbrand

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=20211102201122.3188108-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.