From: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com>,
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
Subject: Re: [Qemu-devel] [PATCH v4 00/11] basic channel IO passthrough infrastructure based on vfio
Date: Tue, 11 Apr 2017 17:34:35 +0800 [thread overview]
Message-ID: <20170411093435.GC2730@bjsdjshi@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170411110658.2bf778e3.cornelia.huck@de.ibm.com>
* Cornelia Huck <cornelia.huck@de.ibm.com> [2017-04-11 11:06:58 +0200]:
> On Fri, 17 Mar 2017 04:19:17 +0100
> Dong Jia Shi <bjsdjshi@linux.vnet.ibm.com> wrote:
>
> > The patch series introduce a basic channel I/O passthrough
> > infrastructure based on vfio.
>
> I think this is basically ready for 2.10, once the kernel changes hit
> master (they are queued in the s390 tree).
:>
>
> (...)
>
> > default-configs/s390x-softmmu.mak | 1 +
> > hw/s390x/Makefile.objs | 1 +
> > hw/s390x/css-bridge.c | 2 +
> > hw/s390x/css.c | 290 ++++++++++++++++++++++--
> > hw/s390x/s390-ccw.c | 137 ++++++++++++
> > hw/s390x/s390-ccw.h | 39 ++++
> > hw/s390x/s390-virtio-ccw.c | 35 ++-
> > hw/s390x/virtio-ccw.c | 7 +-
> > hw/vfio/Makefile.objs | 1 +
> > hw/vfio/ccw.c | 442 +++++++++++++++++++++++++++++++++++++
> > include/hw/s390x/css-bridge.h | 1 +
> > include/hw/s390x/css.h | 67 +++---
> > include/hw/s390x/s390-virtio-ccw.h | 1 +
> > include/hw/vfio/vfio-common.h | 1 +
> > linux-headers/linux/vfio.h | 17 ++
> > linux-headers/linux/vfio_ccw.h | 28 +++
> > qemu-options.hx | 6 +-
> > target/s390x/cpu.h | 10 +
> > target/s390x/ioinst.c | 9 +
> > 19 files changed, 1047 insertions(+), 48 deletions(-)
> > create mode 100644 hw/s390x/s390-ccw.c
> > create mode 100644 hw/s390x/s390-ccw.h
> > create mode 100644 hw/vfio/ccw.c
> > create mode 100644 linux-headers/linux/vfio_ccw.h
>
> It's probably best to take this through my tree (pending acks of the
> vfio parts from Alex W.). It probably also would be good to add an s390
> maintainer for hw/vfio/ccw.c (I'd be willing to do that).
>
> Could you please resend on top of git://github.com/cohuck/qemu s390-next
> and add a MAINTAINERS patch as well?
Sure. Will do.
prev parent reply other threads:[~2017-04-11 9:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 3:19 [Qemu-devel] [PATCH v4 00/11] basic channel IO passthrough infrastructure based on vfio Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 01/11] vfio: linux-headers update for vfio-ccw Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 02/11] s390x/css: add s390-squash-mcss machine option Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 03/11] s390x/css: realize css_sch_build_schib Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 04/11] s390x/css: realize css_create_sch Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 05/11] s390x/css: device support for s390-ccw passthrough Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 06/11] vfio/ccw: vfio based subchannel passthrough driver Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 07/11] vfio/ccw: get io region info Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 08/11] vfio/ccw: get irqs info and set the eventfd fd Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 09/11] s390x/css: introduce and realize ccw-request callback Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 10/11] s390x/css: ccw translation infrastructure Dong Jia Shi
2017-03-17 3:19 ` [Qemu-devel] [PATCH v4 11/11] vfio/ccw: update sense data if a unit check is pending Dong Jia Shi
2017-04-11 9:06 ` [Qemu-devel] [PATCH v4 00/11] basic channel IO passthrough infrastructure based on vfio Cornelia Huck
2017-04-11 9:34 ` Dong Jia Shi [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=20170411093435.GC2730@bjsdjshi@linux.vnet.ibm.com \
--to=bjsdjshi@linux.vnet.ibm.com \
--cc=agraf@suse.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@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 \
/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).