[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200205003048-mutt-send-email-mst@kernel.org>
Date: Wed, 5 Feb 2020 00:31:18 -0500
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Jason Wang <jasowang@...hat.com>
Cc: Tiwei Bie <tiwei.bie@...el.com>, linux-kernel@...r.kernel.org,
kvm@...r.kernel.org, virtualization@...ts.linux-foundation.org,
netdev@...r.kernel.org, shahafs@...lanox.com, jgg@...lanox.com,
rob.miller@...adcom.com, haotian.wang@...ive.com,
eperezma@...hat.com, lulu@...hat.com, parav@...lanox.com,
rdunlap@...radead.org, hch@...radead.org, jiri@...lanox.com,
hanand@...inx.com, mhabets@...arflare.com,
maxime.coquelin@...hat.com, lingshan.zhu@...el.com,
dan.daly@...el.com, cunming.liang@...el.com, zhihong.wang@...el.com
Subject: Re: [PATCH] vhost: introduce vDPA based backend
On Wed, Feb 05, 2020 at 11:12:21AM +0800, Jason Wang wrote:
>
> On 2020/2/5 上午10:05, Tiwei Bie wrote:
> > On Tue, Feb 04, 2020 at 02:46:16PM +0800, Jason Wang wrote:
> > > On 2020/2/4 下午2:01, Michael S. Tsirkin wrote:
> > > > On Tue, Feb 04, 2020 at 11:30:11AM +0800, Jason Wang wrote:
> > > > > 5) generate diffs of memory table and using IOMMU API to setup the dma
> > > > > mapping in this method
> > > > Frankly I think that's a bunch of work. Why not a MAP/UNMAP interface?
> > > >
> > > Sure, so that basically VHOST_IOTLB_UPDATE/INVALIDATE I think?
> > Do you mean we let userspace to only use VHOST_IOTLB_UPDATE/INVALIDATE
> > to do the DMA mapping in vhost-vdpa case? When vIOMMU isn't available,
> > userspace will set msg->iova to GPA, otherwise userspace will set
> > msg->iova to GIOVA, and vhost-vdpa module will get HPA from msg->uaddr?
> >
> > Thanks,
> > Tiwei
>
>
> I think so. Michael, do you think this makes sense?
>
> Thanks
to make sure, could you post the suggested argument format for
these ioctls?
>
> >
> > > Thanks
> > >
> > >
Powered by blists - more mailing lists