[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201021104508-mutt-send-email-mst@kernel.org>
Date: Wed, 21 Oct 2020 10:45:44 -0400
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Jason Wang <jasowang@...hat.com>
Cc: virtualization@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, rob.miller@...adcom.com,
lingshan.zhu@...el.com, eperezma@...hat.com, lulu@...hat.com,
shahafs@...lanox.com, hanand@...inx.com, mhabets@...arflare.com,
gdawar@...inx.com, saugatm@...inx.com, vmireyno@...vell.com,
zhangweining@...jie.com.cn, eli@...lanox.com
Subject: Re: [PATCH 0/4] vDPA: API for reporting IOVA range
On Wed, Jun 17, 2020 at 11:29:43AM +0800, Jason Wang wrote:
> Hi All:
>
> This series introduces API for reporing IOVA range. This is a must for
> userspace to work correclty:
>
> - for the process that uses vhost-vDPA directly to properly allocate
> IOVA
> - for VM(qemu), when vIOMMU is not enabled, fail early if GPA is out
> of range
> - for VM(qemu), when vIOMMU is enabled, determine a valid guest
> address width
>
> Please review.
>
> Thanks
OK so what is the plan here? Change begin-end->first-last and repost?
> Jason Wang (4):
> vdpa: introduce config op to get valid iova range
> vdpa_sim: implement get_iova_range bus operation
> vdpa: get_iova_range() is mandatory for device specific DMA
> translation
> vhost: vdpa: report iova range
>
> drivers/vdpa/vdpa.c | 4 ++++
> drivers/vdpa/vdpa_sim/vdpa_sim.c | 11 +++++++++++
> drivers/vhost/vdpa.c | 27 +++++++++++++++++++++++++++
> include/linux/vdpa.h | 14 ++++++++++++++
> include/uapi/linux/vhost.h | 4 ++++
> include/uapi/linux/vhost_types.h | 5 +++++
> 6 files changed, 65 insertions(+)
>
> --
> 2.20.1
Powered by blists - more mailing lists