On Thu, 9 Mar 2017 17:25:25 +0800 Dong Jia Shi <bjsdjshi@xxxxxxxxxxxxxxxxxx> wrote: > * Dong Jia Shi <bjsdjshi@xxxxxxxxxxxxxxxxxx> [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. -- To unsubscribe from this list: send the line "unsubscribe linux-s390" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
