From: Eric Farman <farman@linux.ibm.com>
To: linux-s390@vger.kernel.org, kvm@vger.kernel.org
Cc: Cornelia Huck <cohuck@redhat.com>,
Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
Jared Rossi <jrossi@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>
Subject: [PATCH v4 0/8] s390x/vfio-ccw: Channel Path Handling [KVM]
Date: Tue, 5 May 2020 14:27:37 +0200 [thread overview]
Message-ID: <20200505122745.53208-1-farman@linux.ibm.com> (raw)
Here is a new pass at the channel-path handling code for vfio-ccw.
Changes from previous versions are recorded in git notes for each patch.
Patches 5 through 7 got swizzled a little bit, in order to better
compartmentalize the code they define. Basically, the IRQ definitions
were moved from patch 7 to 5, and then patch 6 was placed ahead of
patch 5.
I have put Conny's r-b's on patches 1, 3, 4, (new) 5, and 8, and believe
I have addressed all comments from v3, with two exceptions:
> I'm wondering if we should make this [vfio_ccw_schib_region_{write,release}]
> callback optional (not in this patch).
I have that implemented on top of this series, and will send later as part
of a larger cleanup series.
> One thing though that keeps coming up: do we need any kind of
> serialization? Can there be any confusion from concurrent reads from
> userspace, or are we sure that we always provide consistent data?
I _think_ this is in good shape, though as suggested another set of
eyeballs would be nice. There is still a problem on the main
interrupt/FSM path, which I'm not attempting to address here.
With this code plus the corresponding QEMU series (posted momentarily)
applied I am able to configure off/on a CHPID (for example, by issuing
"chchp -c 0/1 xx" on the host), and the guest is able to see both the
events and reflect the updated path masks in its structures.
v3: https://lore.kernel.org/kvm/20200417023001.65006-1-farman@linux.ibm.com/
v2: https://lore.kernel.org/kvm/20200206213825.11444-1-farman@linux.ibm.com/
v1: https://lore.kernel.org/kvm/20191115025620.19593-1-farman@linux.ibm.com/
Eric Farman (3):
vfio-ccw: Refactor the unregister of the async regions
vfio-ccw: Refactor IRQ handlers
vfio-ccw: Add trace for CRW event
Farhan Ali (5):
vfio-ccw: Introduce new helper functions to free/destroy regions
vfio-ccw: Register a chp_event callback for vfio-ccw
vfio-ccw: Introduce a new schib region
vfio-ccw: Introduce a new CRW region
vfio-ccw: Wire up the CRW irq and CRW region
Documentation/s390/vfio-ccw.rst | 38 ++++++-
drivers/s390/cio/Makefile | 2 +-
drivers/s390/cio/vfio_ccw_chp.c | 148 +++++++++++++++++++++++++
drivers/s390/cio/vfio_ccw_drv.c | 165 ++++++++++++++++++++++++++--
drivers/s390/cio/vfio_ccw_ops.c | 65 ++++++++---
drivers/s390/cio/vfio_ccw_private.h | 16 +++
drivers/s390/cio/vfio_ccw_trace.c | 1 +
drivers/s390/cio/vfio_ccw_trace.h | 30 +++++
include/uapi/linux/vfio.h | 3 +
include/uapi/linux/vfio_ccw.h | 18 +++
10 files changed, 458 insertions(+), 28 deletions(-)
create mode 100644 drivers/s390/cio/vfio_ccw_chp.c
--
2.17.1
next reply other threads:[~2020-05-05 12:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 12:27 Eric Farman [this message]
2020-05-05 12:27 ` [PATCH v4 1/8] vfio-ccw: Introduce new helper functions to free/destroy regions Eric Farman
2020-05-05 12:27 ` [PATCH v4 2/8] vfio-ccw: Register a chp_event callback for vfio-ccw Eric Farman
2020-05-06 13:18 ` Cornelia Huck
2020-05-05 12:27 ` [PATCH v4 3/8] vfio-ccw: Refactor the unregister of the async regions Eric Farman
2020-05-05 12:27 ` [PATCH v4 4/8] vfio-ccw: Introduce a new schib region Eric Farman
2020-05-05 12:27 ` [PATCH v4 5/8] vfio-ccw: Refactor IRQ handlers Eric Farman
2020-05-05 12:27 ` [PATCH v4 6/8] vfio-ccw: Introduce a new CRW region Eric Farman
2020-05-06 13:24 ` Cornelia Huck
2020-05-05 12:27 ` [PATCH v4 7/8] vfio-ccw: Wire up the CRW irq and " Eric Farman
2020-05-06 13:52 ` Cornelia Huck
2020-05-05 12:27 ` [PATCH v4 8/8] vfio-ccw: Add trace for CRW event Eric Farman
2020-05-05 12:56 ` [PATCH v4 0/8] s390x/vfio-ccw: Channel Path Handling [KVM] Cornelia Huck
2020-05-05 13:00 ` Eric Farman
2020-05-06 13:59 ` Cornelia Huck
2020-05-18 10:05 ` Cornelia Huck
2020-05-18 10:14 ` 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=20200505122745.53208-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=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.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).