From: Eric Farman <farman@linux.ibm.com>
To: qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Jared Rossi <jrossi@linux.ibm.com>
Subject: [RFC PATCH v1 0/8] s390x/vfio-ccw: Channel Path Handling
Date: Fri, 15 Nov 2019 04:34:29 +0100 [thread overview]
Message-ID: <20191115033437.37926-1-farman@linux.ibm.com> (raw)
Here is a first pass at the channel-path handling code for vfio-ccw,
to take advantage of the corresponding kernel patches posted here:
https://lore.kernel.org/kvm/20191115025620.19593-1-farman@linux.ibm.com/
As with the KVM patches, these were originally written by Farhan Ali
this past summer, and my git notes log the changes I've made since
picking up this work. There are two commits at the front of this
series that seem to be pre-reqs to the actual changes for this, which
is why the linux-headers update seems lost in the middle of this.
I've tried to be mindful of testing permutations of new/old kernel with
either new/old QEMU, and it seems to be in good shape.
Eric Farman (2):
vfio-ccw: Refactor cleanup of regions
vfio-ccw: Refactor ccw irq handler
Farhan Ali (6):
vfio-ccw: Return IOINST_CC_NOT_OPERATIONAL for EIO
vfio-ccw: Don't inject an I/O interrupt if the subchannel is not
enabled
linux-headers: update
vfio-ccw: Add support for the schib region
vfio-ccw: Add support for the crw region
vfio-ccw: Add support for the CRW irq
hw/s390x/css.c | 8 +-
hw/s390x/s390-ccw.c | 20 ++++
hw/vfio/ccw.c | 195 +++++++++++++++++++++++++++++----
include/hw/s390x/css.h | 3 +-
include/hw/s390x/s390-ccw.h | 1 +
linux-headers/linux/vfio.h | 3 +
linux-headers/linux/vfio_ccw.h | 10 ++
target/s390x/ioinst.c | 3 +-
8 files changed, 217 insertions(+), 26 deletions(-)
--
2.17.1
next reply other threads:[~2019-11-15 3:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 3:34 Eric Farman [this message]
2019-11-15 3:34 ` [RFC PATCH v1 1/8] vfio-ccw: Return IOINST_CC_NOT_OPERATIONAL for EIO Eric Farman
2019-11-18 18:13 ` Cornelia Huck
2019-11-19 11:23 ` Halil Pasic
2019-11-19 12:02 ` Cornelia Huck
2019-11-19 15:42 ` Eric Farman
2019-11-19 17:59 ` Halil Pasic
2019-11-20 10:11 ` Cornelia Huck
2019-11-19 15:49 ` Eric Farman
2019-11-15 3:34 ` [RFC PATCH v1 2/8] vfio-ccw: Don't inject an I/O interrupt if the subchannel is not enabled Eric Farman
2019-11-18 18:23 ` Cornelia Huck
2019-11-19 15:47 ` Eric Farman
2019-11-15 3:34 ` [RFC PATCH v1 3/8] linux-headers: update Eric Farman
2019-11-15 3:34 ` [RFC PATCH v1 4/8] vfio-ccw: Refactor cleanup of regions Eric Farman
2019-11-20 10:31 ` Cornelia Huck
2019-11-15 3:34 ` [RFC PATCH v1 5/8] vfio-ccw: Add support for the schib region Eric Farman
2019-11-20 11:13 ` Cornelia Huck
2020-01-31 20:15 ` Eric Farman
2020-02-03 10:43 ` Cornelia Huck
2019-11-15 3:34 ` [RFC PATCH v1 6/8] vfio-ccw: Add support for the crw region Eric Farman
2019-11-20 12:30 ` Cornelia Huck
2019-11-15 3:34 ` [RFC PATCH v1 7/8] vfio-ccw: Refactor ccw irq handler Eric Farman
2019-11-20 12:39 ` Cornelia Huck
2019-12-03 20:01 ` Eric Farman
2019-11-15 3:34 ` [RFC PATCH v1 8/8] vfio-ccw: Add support for the CRW irq Eric Farman
2019-11-20 12:50 ` Cornelia Huck
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=20191115033437.37926-1-farman@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=jrossi@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
/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).