From: Jason Gunthorpe <jgg@nvidia.com>
To: "joro@8bytes.org" <joro@8bytes.org>
Cc: "jean-philippe@linaro.org" <jean-philippe@linaro.org>,
"Tian, Kevin" <kevin.tian@intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"stefanha@gmail.com" <stefanha@gmail.com>,
Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Sun, Yi Y" <yi.y.sun@intel.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"Wu, Hao" <hao.wu@intel.com>,
"Tian, Jun J" <jun.j.tian@intel.com>
Subject: Re: (proposal) RE: [PATCH v7 00/16] vfio: expose virtual Shared Virtual Addressing to VMs
Date: Tue, 3 Nov 2020 13:48:51 -0400 [thread overview]
Message-ID: <20201103174851.GS2620339@nvidia.com> (raw)
In-Reply-To: <20201103165539.GN22888@8bytes.org>
On Tue, Nov 03, 2020 at 05:55:40PM +0100, joro@8bytes.org wrote:
> On Tue, Nov 03, 2020 at 11:22:23AM -0400, Jason Gunthorpe wrote:
> > This whole thread was brought up by IDXD which has a SVA driver and
> > now wants to add a vfio-mdev driver too. SVA devices that want to be
> > plugged into VMs are going to be common - this architecture that a SVA
> > driver cannot cover the kvm case seems problematic.
>
> Isn't that the same pattern as having separate drivers for VFs and the
> parent device in SR-IOV?
I think the same PCI driver with a small flag to support the PF or
VF is not the same as two completely different drivers in different
subsystems
Jason
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Jason Gunthorpe <jgg@nvidia.com>
To: "joro@8bytes.org" <joro@8bytes.org>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
Jason Wang <jasowang@redhat.com>,
"Liu, Yi L" <yi.l.liu@intel.com>,
"alex.williamson@redhat.com" <alex.williamson@redhat.com>,
"eric.auger@redhat.com" <eric.auger@redhat.com>,
"baolu.lu@linux.intel.com" <baolu.lu@linux.intel.com>,
"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.intel.com>,
"Raj, Ashok" <ashok.raj@intel.com>,
"Tian, Jun J" <jun.j.tian@intel.com>,
"Sun, Yi Y" <yi.y.sun@intel.com>,
"jean-philippe@linaro.org" <jean-philippe@linaro.org>,
"peterx@redhat.com" <peterx@redhat.com>,
"Wu, Hao" <hao.wu@intel.com>,
"stefanha@gmail.com" <stefanha@gmail.com>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: (proposal) RE: [PATCH v7 00/16] vfio: expose virtual Shared Virtual Addressing to VMs
Date: Tue, 3 Nov 2020 13:48:51 -0400 [thread overview]
Message-ID: <20201103174851.GS2620339@nvidia.com> (raw)
In-Reply-To: <20201103165539.GN22888@8bytes.org>
On Tue, Nov 03, 2020 at 05:55:40PM +0100, joro@8bytes.org wrote:
> On Tue, Nov 03, 2020 at 11:22:23AM -0400, Jason Gunthorpe wrote:
> > This whole thread was brought up by IDXD which has a SVA driver and
> > now wants to add a vfio-mdev driver too. SVA devices that want to be
> > plugged into VMs are going to be common - this architecture that a SVA
> > driver cannot cover the kvm case seems problematic.
>
> Isn't that the same pattern as having separate drivers for VFs and the
> parent device in SR-IOV?
I think the same PCI driver with a small flag to support the PF or
VF is not the same as two completely different drivers in different
subsystems
Jason
next prev parent reply other threads:[~2020-11-03 17:49 UTC|newest]
Thread overview: 110+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 8:38 (proposal) RE: [PATCH v7 00/16] vfio: expose virtual Shared Virtual Addressing to VMs Tian, Kevin
2020-10-12 8:38 ` Tian, Kevin
2020-10-13 6:22 ` Jason Wang
2020-10-13 6:22 ` Jason Wang
2020-10-14 3:08 ` Tian, Kevin
2020-10-14 3:08 ` Tian, Kevin
2020-10-14 23:10 ` Alex Williamson
2020-10-14 23:10 ` Alex Williamson
2020-10-15 7:02 ` Jason Wang
2020-10-15 7:02 ` Jason Wang
2020-10-15 6:52 ` Jason Wang
2020-10-15 6:52 ` Jason Wang
2020-10-15 7:58 ` Tian, Kevin
2020-10-15 7:58 ` Tian, Kevin
2020-10-15 8:40 ` Jason Wang
2020-10-15 8:40 ` Jason Wang
2020-10-15 10:14 ` Liu, Yi L
2020-10-15 10:14 ` Liu, Yi L
2020-10-20 6:18 ` Jason Wang
2020-10-20 6:18 ` Jason Wang
2020-10-20 8:19 ` Liu, Yi L
2020-10-20 8:19 ` Liu, Yi L
2020-10-20 9:19 ` Jason Wang
2020-10-20 9:19 ` Jason Wang
2020-10-20 9:40 ` Liu, Yi L
2020-10-20 9:40 ` Liu, Yi L
2020-10-20 13:54 ` Jason Gunthorpe
2020-10-20 13:54 ` Jason Gunthorpe
2020-10-20 14:00 ` Liu, Yi L
2020-10-20 14:00 ` Liu, Yi L
2020-10-20 14:05 ` Jason Gunthorpe
2020-10-20 14:05 ` Jason Gunthorpe
2020-10-20 14:09 ` Liu, Yi L
2020-10-20 14:09 ` Liu, Yi L
2020-10-13 10:27 ` Jean-Philippe Brucker
2020-10-13 10:27 ` Jean-Philippe Brucker
2020-10-14 2:11 ` Tian, Kevin
2020-10-14 2:11 ` Tian, Kevin
2020-10-14 3:16 ` Tian, Kevin
2020-10-14 3:16 ` Tian, Kevin
2020-10-16 15:36 ` Jason Gunthorpe
2020-10-16 15:36 ` Jason Gunthorpe
2020-10-19 8:39 ` Liu, Yi L
2020-10-19 8:39 ` Liu, Yi L
2020-10-19 14:25 ` Jason Gunthorpe
2020-10-19 14:25 ` Jason Gunthorpe
2020-10-20 10:21 ` Liu, Yi L
2020-10-20 10:21 ` Liu, Yi L
2020-10-20 14:02 ` Jason Gunthorpe
2020-10-20 14:02 ` Jason Gunthorpe
2020-10-20 14:19 ` Liu, Yi L
2020-10-20 14:19 ` Liu, Yi L
2020-10-21 2:21 ` Jason Wang
2020-10-21 2:21 ` Jason Wang
2020-10-20 16:24 ` Raj, Ashok
2020-10-20 16:24 ` Raj, Ashok
2020-10-20 17:03 ` Jason Gunthorpe
2020-10-20 17:03 ` Jason Gunthorpe
2020-10-20 19:51 ` Raj, Ashok
2020-10-20 19:51 ` Raj, Ashok
2020-10-20 19:55 ` Jason Gunthorpe
2020-10-20 19:55 ` Jason Gunthorpe
2020-10-20 20:08 ` Raj, Ashok
2020-10-20 20:08 ` Raj, Ashok
2020-10-20 20:14 ` Jason Gunthorpe
2020-10-20 20:14 ` Jason Gunthorpe
2020-10-20 20:27 ` Raj, Ashok
2020-10-20 20:27 ` Raj, Ashok
2020-10-21 11:48 ` Jason Gunthorpe
2020-10-21 11:48 ` Jason Gunthorpe
2020-10-21 17:51 ` Raj, Ashok
2020-10-21 17:51 ` Raj, Ashok
2020-10-21 18:24 ` Jason Gunthorpe
2020-10-21 18:24 ` Jason Gunthorpe
2020-10-21 20:03 ` Raj, Ashok
2020-10-21 20:03 ` Raj, Ashok
2020-10-21 23:32 ` Jason Gunthorpe
2020-10-21 23:32 ` Jason Gunthorpe
2020-10-21 23:53 ` Raj, Ashok
2020-10-21 23:53 ` Raj, Ashok
2020-10-22 2:55 ` Jason Wang
2020-10-22 2:55 ` Jason Wang
2020-10-22 3:54 ` Liu, Yi L
2020-10-22 3:54 ` Liu, Yi L
2020-10-22 4:38 ` Jason Wang
2020-10-22 4:38 ` Jason Wang
2020-11-03 9:52 ` joro
2020-11-03 9:52 ` joro
2020-11-03 12:56 ` Jason Gunthorpe
2020-11-03 12:56 ` Jason Gunthorpe
2020-11-03 13:18 ` joro
2020-11-03 13:18 ` joro
2020-11-03 13:23 ` Jason Gunthorpe
2020-11-03 13:23 ` Jason Gunthorpe
2020-11-03 14:03 ` joro
2020-11-03 14:03 ` joro
2020-11-03 14:06 ` Jason Gunthorpe
2020-11-03 14:06 ` Jason Gunthorpe
2020-11-03 14:35 ` joro
2020-11-03 14:35 ` joro
2020-11-03 15:22 ` Jason Gunthorpe
2020-11-03 15:22 ` Jason Gunthorpe
2020-11-03 16:55 ` joro
2020-11-03 16:55 ` joro
2020-11-03 17:48 ` Jason Gunthorpe [this message]
2020-11-03 17:48 ` Jason Gunthorpe
2020-11-03 19:14 ` joro
2020-11-03 19:14 ` joro
2020-11-04 19:29 ` Jason Gunthorpe
2020-11-04 19:29 ` Jason Gunthorpe
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=20201103174851.GS2620339@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=hao.wu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jasowang@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=jun.j.tian@intel.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=stefanha@gmail.com \
--cc=yi.y.sun@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.