From: Cornelia Huck <cohuck@redhat.com>
To: Eric Farman <farman@linux.ibm.com>
Cc: Halil Pasic <pasic@linux.ibm.com>,
Jason Herne <jjherne@linux.ibm.com>,
qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
Jared Rossi <jrossi@linux.ibm.com>
Subject: Re: [PATCH v4 0/6] s390x/vfio-ccw: Channel Path Handling [QEMU]
Date: Tue, 16 Jun 2020 19:01:15 +0200 [thread overview]
Message-ID: <20200616190115.27c8497f.cohuck@redhat.com> (raw)
In-Reply-To: <20200505125757.98209-1-farman@linux.ibm.com>
On Tue, 5 May 2020 14:57:51 +0200
Eric Farman <farman@linux.ibm.com> wrote:
> Here is a new 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/20200505122745.53208-1-farman@linux.ibm.com/
>
> I have all the main comments from v3 addressed, though I have a
> couple of additional patches that do some further cleanups
> (like, a generic callback for stsch) that weren't baked enough
> to include here. They're working fine, but need some cleanups
> (e.g., fixups vs standalone patches) before they're ready for
> submission. Just wanted to have the basic QEMU code to go with
> the new KVM series.
>
> Changes are listed in git notes for the individual patches.
>
> v3: https://lore.kernel.org/qemu-devel/20200417023440.70514-1-farman@linux.ibm.com/
> v2: https://lore.kernel.org/qemu-devel/20200206214509.16434-1-farman@linux.ibm.com/
> v1: https://lore.kernel.org/qemu-devel/20191115033437.37926-1-farman@linux.ibm.com/
>
> Eric Farman (3):
> vfio-ccw: Refactor cleanup of regions
> vfio-ccw: Refactor ccw irq handler
> s390x/css: Refactor the css_queue_crw() routine
>
> Farhan Ali (3):
> linux-headers: update
> vfio-ccw: Add support for the schib region
> vfio-ccw: Add support for the CRW region and IRQ
>
> hw/s390x/css.c | 57 ++++++---
> hw/s390x/s390-ccw.c | 21 ++++
> hw/vfio/ccw.c | 208 +++++++++++++++++++++++++++++----
> include/hw/s390x/css.h | 4 +-
> include/hw/s390x/s390-ccw.h | 1 +
> linux-headers/linux/vfio.h | 3 +
> linux-headers/linux/vfio_ccw.h | 18 +++
> target/s390x/ioinst.c | 3 +-
> 8 files changed, 274 insertions(+), 41 deletions(-)
>
Thanks, replaced patch 1 with a proper headers update against 5.8-rc1
and applied.
prev parent reply other threads:[~2020-06-16 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 12:57 [PATCH v4 0/6] s390x/vfio-ccw: Channel Path Handling [QEMU] Eric Farman
2020-05-05 12:57 ` [PATCH v4 1/6] linux-headers: update Eric Farman
2020-05-05 12:57 ` [PATCH v4 2/6] vfio-ccw: Refactor cleanup of regions Eric Farman
2020-05-05 12:57 ` [PATCH v4 3/6] vfio-ccw: Add support for the schib region Eric Farman
2020-05-06 15:56 ` Cornelia Huck
2020-05-05 12:57 ` [PATCH v4 4/6] vfio-ccw: Refactor ccw irq handler Eric Farman
2020-05-05 12:57 ` [PATCH v4 5/6] s390x/css: Refactor the css_queue_crw() routine Eric Farman
2020-05-06 15:58 ` Cornelia Huck
2020-05-05 12:57 ` [PATCH v4 6/6] vfio-ccw: Add support for the CRW region and IRQ Eric Farman
2020-05-06 16:01 ` Cornelia Huck
2020-05-06 16:03 ` [PATCH v4 0/6] s390x/vfio-ccw: Channel Path Handling [QEMU] Cornelia Huck
2020-06-16 17:01 ` Cornelia Huck [this message]
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=20200616190115.27c8497f.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=farman@linux.ibm.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).