From: Cornelia Huck <cornelia.huck@de.ibm.com>
To: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org,
qemu-devel@nongnu.org, renxiaof@linux.vnet.ibm.com,
borntraeger@de.ibm.com, agraf@suse.com,
alex.williamson@redhat.com, pmorel@linux.vnet.ibm.com,
pasic@linux.vnet.ibm.com, wkywang@linux.vnet.ibm.com
Subject: Re: [PATCH RFC v3 00/15] basic vfio-ccw infrastructure
Date: Fri, 10 Mar 2017 11:46:05 +0100 [thread overview]
Message-ID: <20170310114605.1353e810.cornelia.huck@de.ibm.com> (raw)
In-Reply-To: <20170309092525.GA10189@bjsdjshi@linux.vnet.ibm.com>
On Thu, 9 Mar 2017 17:25:25 +0800
Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> wrote:
> * Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> [2017-02-17 09:29:24 +0100]:
>
> > vfio-ccw: the basic infrastructure
> > ==================================
> >
> > Introduction
> > ------------
> >
> > Here we describe the vfio support for I/O subchannel devices for
> > Linux/s390. Motivation for vfio-ccw is to passthrough subchannels to a
> > virtual machine, while vfio is the means.
> >
>
> Ping.
>
> Any more comment for this version?
>
> Thanks.
>
> [...]
>
I just walked through the patch set again and did not notice anything
else. There's still the area of channel path handling, but I don't see
why it shouldn't be able to fit into the infrastructure you introduce
here. (I'd expect most of the interesting stuff there to be handled in
user space anyway.)
You should update MAINTAINERS, though. I'm not sure the s390 cio folks
are prepared to handle vfio-ccw :) (although I think you should cc:
them on the patches exporting cio interfaces.) It's probably best to
take vfio-ccw through the kvm-s390 tree.
next prev parent reply other threads:[~2017-03-10 10:46 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 8:29 [PATCH RFC v3 00/15] basic vfio-ccw infrastructure Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 01/15] s390: cio: introduce cio_cancel_halt_clear Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 02/15] s390: cio: export more interfaces Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 03/15] vfio: ccw: define device_api strings Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 04/15] vfio: ccw: basic implementation for vfio_ccw driver Dong Jia Shi
2017-02-20 18:31 ` Cornelia Huck
2017-02-21 7:36 ` Dong Jia Shi
[not found] ` <20170221073623.GJ562@bjsdjshi@linux.vnet.ibm.com>
2017-02-21 7:43 ` Dong Jia Shi
2017-02-21 15:43 ` Cornelia Huck
2017-02-22 3:05 ` Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 05/15] vfio: ccw: introduce channel program interfaces Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 06/15] vfio: ccw: register vfio_ccw to the mediated device framework Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 07/15] vfio: ccw: introduce ccw_io_region Dong Jia Shi
2017-02-24 23:13 ` Alex Williamson
2017-02-17 8:29 ` [PATCH RFC v3 08/15] vfio: ccw: handle ccw command request Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 09/15] vfio: ccw: realize VFIO_DEVICE_GET_REGION_INFO ioctl Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 10/15] vfio: ccw: realize VFIO_DEVICE_RESET ioctl Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 11/15] vfio: ccw: realize VFIO_DEVICE_G(S)ET_IRQ_INFO ioctls Dong Jia Shi
2017-02-24 23:27 ` Alex Williamson
2017-02-27 1:44 ` Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 12/15] vfio: ccw: return I/O results asynchronously Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 13/15] vfio: ccw: introduce a finite state machine Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 14/15] docs: add documentation for vfio-ccw Dong Jia Shi
2017-02-17 8:29 ` [PATCH RFC v3 15/15] vfio: ccw: introduce support for ccw0 Dong Jia Shi
2017-02-20 18:59 ` Cornelia Huck
2017-02-21 8:58 ` Dong Jia Shi
[not found] ` <20170221085824.GN562@bjsdjshi@linux.vnet.ibm.com>
2017-02-21 15:47 ` Cornelia Huck
[not found] ` <20170309092525.GA10189@bjsdjshi@linux.vnet.ibm.com>
2017-03-10 10:46 ` Cornelia Huck [this message]
[not found] ` <20170313071652.GD6756@bjsdjshi@linux.vnet.ibm.com>
2017-03-16 9:25 ` [PATCH RFC v3 00/15] basic vfio-ccw infrastructure 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=20170310114605.1353e810.cornelia.huck@de.ibm.com \
--to=cornelia.huck@de.ibm.com \
--cc=agraf@suse.com \
--cc=alex.williamson@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.vnet.ibm.com \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=renxiaof@linux.vnet.ibm.com \
--cc=wkywang@linux.vnet.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