From: Jason Wang <jasowang@redhat.com>
To: mst@redhat.com, jasowang@redhat.com,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Cc: shahafs@mellanox.com, lulu@redhat.com, saugatm@xilinx.com,
mhabets@solarflare.com, vmireyno@marvell.com, gdawar@xilinx.com,
eperezma@redhat.com, hanand@xilinx.com,
zhangweining@ruijie.com.cn, eli@mellanox.com,
lingshan.zhu@intel.com, rob.miller@broadcom.com
Subject: [PATCH 0/4] vDPA: API for reporting IOVA range
Date: Wed, 17 Jun 2020 11:29:43 +0800 [thread overview]
Message-ID: <20200617032947.6371-1-jasowang@redhat.com> (raw)
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
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
next reply other threads:[~2020-06-17 3:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 3:29 Jason Wang [this message]
2020-06-17 3:29 ` [PATCH 1/4] vdpa: introduce config op to get valid iova range Jason Wang
2020-08-05 12:51 ` Michael S. Tsirkin
2020-08-06 3:25 ` Jason Wang
2020-08-06 5:54 ` Michael S. Tsirkin
[not found] ` <20200806120354.GA171218@mtl-vdi-166.wap.labs.mlnx>
2020-08-06 12:29 ` Michael S. Tsirkin
2020-08-07 3:23 ` Jason Wang
[not found] ` <20200806124354.GA172661@mtl-vdi-166.wap.labs.mlnx>
2020-08-10 12:05 ` Michael S. Tsirkin
2020-08-11 2:53 ` Jason Wang
2020-08-11 8:29 ` Michael S. Tsirkin
2020-08-12 2:02 ` Jason Wang
[not found] ` <20200806121002.GA171574@mtl-vdi-166.wap.labs.mlnx>
2020-08-07 3:04 ` Jason Wang
2020-06-17 3:29 ` [PATCH 2/4] vdpa_sim: implement get_iova_range bus operation Jason Wang
2020-06-17 3:29 ` [PATCH 3/4] vdpa: get_iova_range() is mandatory for device specific DMA translation Jason Wang
2020-08-05 12:55 ` Michael S. Tsirkin
2020-08-06 3:27 ` Jason Wang
2020-06-17 3:29 ` [PATCH 4/4] vhost: vdpa: report iova range Jason Wang
2020-08-05 12:58 ` Michael S. Tsirkin
2020-08-06 3:29 ` Jason Wang
2020-08-06 5:55 ` Michael S. Tsirkin
2020-10-21 14:45 ` [PATCH 0/4] vDPA: API for reporting IOVA range Michael S. Tsirkin
2020-10-22 5:47 ` Jason Wang
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=20200617032947.6371-1-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=eli@mellanox.com \
--cc=eperezma@redhat.com \
--cc=gdawar@xilinx.com \
--cc=hanand@xilinx.com \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mhabets@solarflare.com \
--cc=mst@redhat.com \
--cc=rob.miller@broadcom.com \
--cc=saugatm@xilinx.com \
--cc=shahafs@mellanox.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vmireyno@marvell.com \
--cc=zhangweining@ruijie.com.cn \
/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).