From: Jason Gunthorpe <jgg@nvidia.com>
To: "Raj, Ashok" <ashok.raj@intel.com>
Cc: "Liu, Yi L" <yi.l.liu@intel.com>,
"Tian, Kevin" <kevin.tian@intel.com>,
Jason Wang <jasowang@redhat.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>,
"joro@8bytes.org" <joro@8bytes.org>,
"jacob.jun.pan@linux.intel.com" <jacob.jun.pan@linux.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>,
"Zhu, Lingshan" <lingshan.zhu@intel.com>
Subject: Re: (proposal) RE: [PATCH v7 00/16] vfio: expose virtual Shared Virtual Addressing to VMs
Date: Wed, 21 Oct 2020 08:48:29 -0300 [thread overview]
Message-ID: <20201021114829.GR6219@nvidia.com> (raw)
In-Reply-To: <20201020202713.GF86371@otc-nc-03>
On Tue, Oct 20, 2020 at 01:27:13PM -0700, Raj, Ashok wrote:
> On Tue, Oct 20, 2020 at 05:14:03PM -0300, Jason Gunthorpe wrote:
> > On Tue, Oct 20, 2020 at 01:08:44PM -0700, Raj, Ashok wrote:
> > > On Tue, Oct 20, 2020 at 04:55:57PM -0300, Jason Gunthorpe wrote:
> > > > On Tue, Oct 20, 2020 at 12:51:46PM -0700, Raj, Ashok wrote:
> > > > > I think we agreed (or agree to disagree and commit) for device types that
> > > > > we have for SIOV, VFIO based approach works well without having to re-invent
> > > > > another way to do the same things. Not looking for a shortcut by any means,
> > > > > but we need to plan around existing hardware though. Looks like vDPA took
> > > > > some shortcuts then to not abstract iommu uAPI instead :-)? When all
> > > > > necessary hardware was available.. This would be a solved puzzle.
> > > >
> > > > I think it is the opposite, vIOMMU and related has outgrown VFIO as
> > > > the "home" and needs to stand alone.
> > > >
> > > > Apparently the HW that will need PASID for vDPA is Intel HW, so if
> > >
> > > So just to make this clear, I did check internally if there are any plans
> > > for vDPA + SVM. There are none at the moment.
> >
> > Not SVM, SIOV.
>
> ... And that included.. I should have said vDPA + PASID, No current plans.
> I have no idea who set expectations with you. Can you please put me in touch
> with that person, privately is fine.
It was the team that aruged VDPA had to be done through VFIO - SIOV
and PASID was one of their reasons it had to be VFIO, check the list
archives
If they didn't plan to use it, bit of a strawman argument, right?
Jason
next prev parent reply other threads:[~2020-10-21 11:48 UTC|newest]
Thread overview: 55+ 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-13 6:22 ` Jason Wang
2020-10-14 3:08 ` Tian, Kevin
2020-10-14 23:10 ` Alex Williamson
2020-10-15 7:02 ` Jason Wang
2020-10-15 6:52 ` Jason Wang
2020-10-15 7:58 ` Tian, Kevin
2020-10-15 8:40 ` Jason Wang
2020-10-15 10:14 ` Liu, Yi L
2020-10-20 6:18 ` Jason Wang
2020-10-20 8:19 ` Liu, Yi L
2020-10-20 9:19 ` Jason Wang
2020-10-20 9:40 ` Liu, Yi L
2020-10-20 13:54 ` Jason Gunthorpe
2020-10-20 14:00 ` Liu, Yi L
2020-10-20 14:05 ` Jason Gunthorpe
2020-10-20 14:09 ` Liu, Yi L
2020-10-13 10:27 ` Jean-Philippe Brucker
2020-10-14 2:11 ` Tian, Kevin
2020-10-14 3:16 ` Tian, Kevin
2020-10-16 15:36 ` Jason Gunthorpe
2020-10-19 8:39 ` Liu, Yi L
2020-10-19 14:25 ` Jason Gunthorpe
2020-10-20 10:21 ` Liu, Yi L
2020-10-20 14:02 ` Jason Gunthorpe
2020-10-20 14:19 ` Liu, Yi L
2020-10-21 2:21 ` Jason Wang
2020-10-20 16:24 ` Raj, Ashok
2020-10-20 17:03 ` Jason Gunthorpe
2020-10-20 19:51 ` Raj, Ashok
2020-10-20 19:55 ` Jason Gunthorpe
2020-10-20 20:08 ` Raj, Ashok
2020-10-20 20:14 ` Jason Gunthorpe
2020-10-20 20:27 ` Raj, Ashok
2020-10-21 11:48 ` Jason Gunthorpe [this message]
2020-10-21 17:51 ` Raj, Ashok
2020-10-21 18:24 ` Jason Gunthorpe
2020-10-21 20:03 ` Raj, Ashok
2020-10-21 23:32 ` Jason Gunthorpe
2020-10-21 23:53 ` Raj, Ashok
2020-10-22 2:55 ` Jason Wang
2020-10-22 3:54 ` Liu, Yi L
2020-10-22 4:38 ` Jason Wang
2020-11-03 9:52 ` joro
2020-11-03 12:56 ` Jason Gunthorpe
2020-11-03 13:18 ` joro
2020-11-03 13:23 ` Jason Gunthorpe
2020-11-03 14:03 ` joro
2020-11-03 14:06 ` Jason Gunthorpe
2020-11-03 14:35 ` joro
2020-11-03 15:22 ` Jason Gunthorpe
2020-11-03 16:55 ` joro
2020-11-03 17:48 ` Jason Gunthorpe
2020-11-03 19:14 ` joro
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=20201021114829.GR6219@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=baolu.lu@linux.intel.com \
--cc=eric.auger@redhat.com \
--cc=hao.wu@intel.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--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=lingshan.zhu@intel.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=stefanha@gmail.com \
--cc=yi.l.liu@intel.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 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).