From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Subject: Re: [PATCH v4 00/16] basic vfio-ccw infrastructure Date: Tue, 28 Mar 2017 10:39:40 +0200 Message-ID: References: <20170317031743.40128-1-bjsdjshi@linux.vnet.ibm.com> <20170328102016.4926f21d.cornelia.huck@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20170328102016.4926f21d.cornelia.huck@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-Archive: List-Post: To: Cornelia Huck , Dong Jia Shi Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org, qemu-devel@nongnu.org, renxiaof@linux.vnet.ibm.com, agraf@suse.com, alex.williamson@redhat.com, pmorel@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com, Martin Schwidefsky , Paolo Bonzini Alex Williamson List-ID: On 03/28/2017 10:20 AM, Cornelia Huck wrote: > On Fri, 17 Mar 2017 04:17:27 +0100 > Dong Jia Shi wrote: > >> Dong Jia Shi (16): >> s390: cio: introduce cio_cancel_halt_clear >> s390: cio: export more interfaces >> vfio: ccw: define device_api strings >> vfio: ccw: basic implementation for vfio_ccw driver >> vfio: ccw: introduce channel program interfaces >> vfio: ccw: register vfio_ccw to the mediated device framework >> vfio: ccw: introduce ccw_io_region >> vfio: ccw: handle ccw command request >> vfio: ccw: realize VFIO_DEVICE_GET_REGION_INFO ioctl >> vfio: ccw: realize VFIO_DEVICE_RESET ioctl >> vfio: ccw: realize VFIO_DEVICE_G(S)ET_IRQ_INFO ioctls >> vfio: ccw: return I/O results asynchronously >> vfio: ccw: introduce a finite state machine >> docs: add documentation for vfio-ccw >> vfio: ccw: introduce support for ccw0 >> MAINTAINERS: Add vfio-ccw maintainers >> >> Documentation/s390/00-INDEX | 2 + >> Documentation/s390/vfio-ccw.txt | 303 +++++++++++++ >> MAINTAINERS | 10 + >> arch/s390/Kconfig | 10 + >> arch/s390/include/asm/cio.h | 18 + >> arch/s390/include/asm/isc.h | 1 + >> drivers/iommu/Kconfig | 8 + >> drivers/s390/cio/Makefile | 3 + >> drivers/s390/cio/cio.c | 69 +++ >> drivers/s390/cio/cio.h | 1 + >> drivers/s390/cio/device_fsm.c | 54 +-- >> drivers/s390/cio/vfio_ccw_cp.c | 842 ++++++++++++++++++++++++++++++++++++ >> drivers/s390/cio/vfio_ccw_cp.h | 42 ++ >> drivers/s390/cio/vfio_ccw_drv.c | 308 +++++++++++++ >> drivers/s390/cio/vfio_ccw_fsm.c | 207 +++++++++ >> drivers/s390/cio/vfio_ccw_ops.c | 447 +++++++++++++++++++ >> drivers/s390/cio/vfio_ccw_private.h | 96 ++++ >> include/uapi/linux/vfio.h | 18 + >> include/uapi/linux/vfio_ccw.h | 24 + >> 19 files changed, 2417 insertions(+), 46 deletions(-) >> create mode 100644 Documentation/s390/vfio-ccw.txt >> create mode 100644 drivers/s390/cio/vfio_ccw_cp.c >> create mode 100644 drivers/s390/cio/vfio_ccw_cp.h >> create mode 100644 drivers/s390/cio/vfio_ccw_drv.c >> create mode 100644 drivers/s390/cio/vfio_ccw_fsm.c >> create mode 100644 drivers/s390/cio/vfio_ccw_ops.c >> create mode 100644 drivers/s390/cio/vfio_ccw_private.h >> create mode 100644 include/uapi/linux/vfio_ccw.h >> > > Patch set looks good to me, and I think we should target it for the > next merge window (the interface looks fine, and we can iron out any > other things later.) > > Question: Which tree should this go through? Vfio or kvm/s390? Reading todays MAINTAINERS file this would go via Martins tree, after the last patch it will be separate. I can certainly carry that via the kvms390 tree, but Alex is certainly the final maintainer. So what about having a new repository under https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/ e.g. vfio.git that will then queue the patches for Alex to take? From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Subject: Re: [PATCH v4 00/16] basic vfio-ccw infrastructure Date: Tue, 28 Mar 2017 10:39:40 +0200 Message-ID: References: <20170317031743.40128-1-bjsdjshi@linux.vnet.ibm.com> <20170328102016.4926f21d.cornelia.huck@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org, qemu-devel@nongnu.org, renxiaof@linux.vnet.ibm.com, agraf@suse.com, alex.williamson@redhat.com, pmorel@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com, Martin Schwidefsky , Paolo Bonzini , Alex Williamson To: Cornelia Huck , Dong Jia Shi Return-path: Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:52154 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754641AbdC1Ijv (ORCPT ); Tue, 28 Mar 2017 04:39:51 -0400 Received: from pps.filterd (m0098404.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2S8dJ85042693 for ; Tue, 28 Mar 2017 04:39:50 -0400 Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0a-001b2d01.pphosted.com with ESMTP id 29fm1jswd7-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 28 Mar 2017 04:39:49 -0400 Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 28 Mar 2017 02:39:48 -0600 In-Reply-To: <20170328102016.4926f21d.cornelia.huck@de.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: On 03/28/2017 10:20 AM, Cornelia Huck wrote: > On Fri, 17 Mar 2017 04:17:27 +0100 > Dong Jia Shi wrote: > >> Dong Jia Shi (16): >> s390: cio: introduce cio_cancel_halt_clear >> s390: cio: export more interfaces >> vfio: ccw: define device_api strings >> vfio: ccw: basic implementation for vfio_ccw driver >> vfio: ccw: introduce channel program interfaces >> vfio: ccw: register vfio_ccw to the mediated device framework >> vfio: ccw: introduce ccw_io_region >> vfio: ccw: handle ccw command request >> vfio: ccw: realize VFIO_DEVICE_GET_REGION_INFO ioctl >> vfio: ccw: realize VFIO_DEVICE_RESET ioctl >> vfio: ccw: realize VFIO_DEVICE_G(S)ET_IRQ_INFO ioctls >> vfio: ccw: return I/O results asynchronously >> vfio: ccw: introduce a finite state machine >> docs: add documentation for vfio-ccw >> vfio: ccw: introduce support for ccw0 >> MAINTAINERS: Add vfio-ccw maintainers >> >> Documentation/s390/00-INDEX | 2 + >> Documentation/s390/vfio-ccw.txt | 303 +++++++++++++ >> MAINTAINERS | 10 + >> arch/s390/Kconfig | 10 + >> arch/s390/include/asm/cio.h | 18 + >> arch/s390/include/asm/isc.h | 1 + >> drivers/iommu/Kconfig | 8 + >> drivers/s390/cio/Makefile | 3 + >> drivers/s390/cio/cio.c | 69 +++ >> drivers/s390/cio/cio.h | 1 + >> drivers/s390/cio/device_fsm.c | 54 +-- >> drivers/s390/cio/vfio_ccw_cp.c | 842 ++++++++++++++++++++++++++++++++++++ >> drivers/s390/cio/vfio_ccw_cp.h | 42 ++ >> drivers/s390/cio/vfio_ccw_drv.c | 308 +++++++++++++ >> drivers/s390/cio/vfio_ccw_fsm.c | 207 +++++++++ >> drivers/s390/cio/vfio_ccw_ops.c | 447 +++++++++++++++++++ >> drivers/s390/cio/vfio_ccw_private.h | 96 ++++ >> include/uapi/linux/vfio.h | 18 + >> include/uapi/linux/vfio_ccw.h | 24 + >> 19 files changed, 2417 insertions(+), 46 deletions(-) >> create mode 100644 Documentation/s390/vfio-ccw.txt >> create mode 100644 drivers/s390/cio/vfio_ccw_cp.c >> create mode 100644 drivers/s390/cio/vfio_ccw_cp.h >> create mode 100644 drivers/s390/cio/vfio_ccw_drv.c >> create mode 100644 drivers/s390/cio/vfio_ccw_fsm.c >> create mode 100644 drivers/s390/cio/vfio_ccw_ops.c >> create mode 100644 drivers/s390/cio/vfio_ccw_private.h >> create mode 100644 include/uapi/linux/vfio_ccw.h >> > > Patch set looks good to me, and I think we should target it for the > next merge window (the interface looks fine, and we can iron out any > other things later.) > > Question: Which tree should this go through? Vfio or kvm/s390? Reading todays MAINTAINERS file this would go via Martins tree, after the last patch it will be separate. I can certainly carry that via the kvms390 tree, but Alex is certainly the final maintainer. So what about having a new repository under https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/ e.g. vfio.git that will then queue the patches for Alex to take? From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35538) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1csmfT-0002B0-C7 for qemu-devel@nongnu.org; Tue, 28 Mar 2017 04:39:56 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1csmfQ-0002Xx-A8 for qemu-devel@nongnu.org; Tue, 28 Mar 2017 04:39:55 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:56116 helo=mx0a-001b2d01.pphosted.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1csmfQ-0002XY-3d for qemu-devel@nongnu.org; Tue, 28 Mar 2017 04:39:52 -0400 Received: from pps.filterd (m0098421.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2S8YeXD093164 for ; Tue, 28 Mar 2017 04:39:50 -0400 Received: from e31.co.us.ibm.com (e31.co.us.ibm.com [32.97.110.149]) by mx0a-001b2d01.pphosted.com with ESMTP id 29fkw824kn-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for ; Tue, 28 Mar 2017 04:39:50 -0400 Received: from localhost by e31.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Tue, 28 Mar 2017 02:39:48 -0600 References: <20170317031743.40128-1-bjsdjshi@linux.vnet.ibm.com> <20170328102016.4926f21d.cornelia.huck@de.ibm.com> From: Christian Borntraeger Date: Tue, 28 Mar 2017 10:39:40 +0200 MIME-Version: 1.0 In-Reply-To: <20170328102016.4926f21d.cornelia.huck@de.ibm.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Message-Id: Subject: Re: [Qemu-devel] [PATCH v4 00/16] basic vfio-ccw infrastructure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Cornelia Huck , Dong Jia Shi Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org, qemu-devel@nongnu.org, renxiaof@linux.vnet.ibm.com, agraf@suse.com, alex.williamson@redhat.com, pmorel@linux.vnet.ibm.com, pasic@linux.vnet.ibm.com, Martin Schwidefsky , Paolo Bonzini Alex Williamson On 03/28/2017 10:20 AM, Cornelia Huck wrote: > On Fri, 17 Mar 2017 04:17:27 +0100 > Dong Jia Shi wrote: > >> Dong Jia Shi (16): >> s390: cio: introduce cio_cancel_halt_clear >> s390: cio: export more interfaces >> vfio: ccw: define device_api strings >> vfio: ccw: basic implementation for vfio_ccw driver >> vfio: ccw: introduce channel program interfaces >> vfio: ccw: register vfio_ccw to the mediated device framework >> vfio: ccw: introduce ccw_io_region >> vfio: ccw: handle ccw command request >> vfio: ccw: realize VFIO_DEVICE_GET_REGION_INFO ioctl >> vfio: ccw: realize VFIO_DEVICE_RESET ioctl >> vfio: ccw: realize VFIO_DEVICE_G(S)ET_IRQ_INFO ioctls >> vfio: ccw: return I/O results asynchronously >> vfio: ccw: introduce a finite state machine >> docs: add documentation for vfio-ccw >> vfio: ccw: introduce support for ccw0 >> MAINTAINERS: Add vfio-ccw maintainers >> >> Documentation/s390/00-INDEX | 2 + >> Documentation/s390/vfio-ccw.txt | 303 +++++++++++++ >> MAINTAINERS | 10 + >> arch/s390/Kconfig | 10 + >> arch/s390/include/asm/cio.h | 18 + >> arch/s390/include/asm/isc.h | 1 + >> drivers/iommu/Kconfig | 8 + >> drivers/s390/cio/Makefile | 3 + >> drivers/s390/cio/cio.c | 69 +++ >> drivers/s390/cio/cio.h | 1 + >> drivers/s390/cio/device_fsm.c | 54 +-- >> drivers/s390/cio/vfio_ccw_cp.c | 842 ++++++++++++++++++++++++++++++++++++ >> drivers/s390/cio/vfio_ccw_cp.h | 42 ++ >> drivers/s390/cio/vfio_ccw_drv.c | 308 +++++++++++++ >> drivers/s390/cio/vfio_ccw_fsm.c | 207 +++++++++ >> drivers/s390/cio/vfio_ccw_ops.c | 447 +++++++++++++++++++ >> drivers/s390/cio/vfio_ccw_private.h | 96 ++++ >> include/uapi/linux/vfio.h | 18 + >> include/uapi/linux/vfio_ccw.h | 24 + >> 19 files changed, 2417 insertions(+), 46 deletions(-) >> create mode 100644 Documentation/s390/vfio-ccw.txt >> create mode 100644 drivers/s390/cio/vfio_ccw_cp.c >> create mode 100644 drivers/s390/cio/vfio_ccw_cp.h >> create mode 100644 drivers/s390/cio/vfio_ccw_drv.c >> create mode 100644 drivers/s390/cio/vfio_ccw_fsm.c >> create mode 100644 drivers/s390/cio/vfio_ccw_ops.c >> create mode 100644 drivers/s390/cio/vfio_ccw_private.h >> create mode 100644 include/uapi/linux/vfio_ccw.h >> > > Patch set looks good to me, and I think we should target it for the > next merge window (the interface looks fine, and we can iron out any > other things later.) > > Question: Which tree should this go through? Vfio or kvm/s390? Reading todays MAINTAINERS file this would go via Martins tree, after the last patch it will be separate. I can certainly carry that via the kvms390 tree, but Alex is certainly the final maintainer. So what about having a new repository under https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/ e.g. vfio.git that will then queue the patches for Alex to take?