From: Srujana Challa <schalla@marvell.com>
To: <virtualization@lists.linux.dev>, <kvm@vger.kernel.org>
Cc: <mst@redhat.com>, <jasowang@redhat.com>, <eperezma@redhat.com>,
<ndabilpuram@marvell.com>, <jerinj@marvell.com>
Subject: [PATCH v2 0/2] vhost-vdpa: Add support for NO-IOMMU mode
Date: Fri, 20 Sep 2024 19:35:28 +0530 [thread overview]
Message-ID: <20240920140530.775307-1-schalla@marvell.com> (raw)
This patchset introduces support for an UNSAFE, no-IOMMU mode in the
vhost-vdpa driver. When enabled, this mode provides no device isolation,
no DMA translation, no host kernel protection, and cannot be used for
device assignment to virtual machines. It requires RAWIO permissions
and will taint the kernel.
This mode requires enabling the "enable_vhost_vdpa_unsafe_noiommu_mode"
option on the vhost-vdpa driver and also negotiate the feature flag
VHOST_BACKEND_F_NOIOMMU. This mode would be useful to get
better performance on specifice low end machines and can be leveraged
by embedded platforms where applications run in controlled environment.
First patch introduces a module parameter
"enable_vhost_vdpa_unsafe_noiommu_mode", while the second patch
introduces a feature flag VHOST_BACKEND_F_NOIOMMU to the vhost vdpa
driver to support NO-IOMMU mode.
This feature flag indicates to userspace that the driver can safely
operate in NO-IOMMU mode. If the flag is not present, userspace should
assume NO-IOMMU mode is unsupported and must not proceed.
v1->v2:
- Introduced new feature flag to vhost backend features for negotiating
NO-IOMMU feature.
Srujana Challa (2):
vhost-vdpa: introduce module parameter for no-IOMMU mode
vhost-vdpa: introduce NO-IOMMU backend feature bit
drivers/vhost/vdpa.c | 39 +++++++++++++++++++++++++++++++-
include/uapi/linux/vhost_types.h | 2 ++
2 files changed, 40 insertions(+), 1 deletion(-)
--
2.25.1
next reply other threads:[~2024-09-20 14:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 14:05 Srujana Challa [this message]
2024-09-20 14:05 ` [PATCH v2 1/2] vhost-vdpa: introduce module parameter for no-IOMMU mode Srujana Challa
2024-09-21 17:28 ` kernel test robot
2024-09-20 14:05 ` [PATCH v2 2/2] vhost-vdpa: introduce NO-IOMMU backend feature bit Srujana Challa
2024-09-24 7:43 ` Jason Wang
2024-09-24 10:01 ` [EXTERNAL] " Srujana Challa
2024-10-01 8:47 ` [PATCH v2 0/2] vhost-vdpa: Add support for NO-IOMMU mode Christoph Hellwig
2024-10-14 13:18 ` [EXTERNAL] " Srujana Challa
2024-10-15 3:48 ` Christoph Hellwig
2024-10-16 17:28 ` Srujana Challa
2024-10-17 6:19 ` Christoph Hellwig
2024-10-17 8:53 ` Srujana Challa
2024-10-18 4:54 ` Jason Wang
2024-10-18 5:24 ` Christoph Hellwig
2024-10-18 13:08 ` Srujana Challa
2024-10-16 17:41 ` Michael S. Tsirkin
2024-10-17 6:16 ` Christoph Hellwig
2024-10-20 0:16 ` Michael S. Tsirkin
2024-10-23 6:58 ` Christoph Hellwig
2024-10-23 8:19 ` Michael S. Tsirkin
2024-10-24 9:05 ` Christoph Hellwig
2024-11-06 12:38 ` Srujana Challa
2024-11-06 15:45 ` Christoph Hellwig
2024-11-07 6:08 ` Srujana Challa
2024-11-12 7:11 ` Srujana Challa
2024-11-06 18:11 ` Michael S. Tsirkin
2024-11-06 18:14 ` Michael S. Tsirkin
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=20240920140530.775307-1-schalla@marvell.com \
--to=schalla@marvell.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=jerinj@marvell.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ndabilpuram@marvell.com \
--cc=virtualization@lists.linux.dev \
/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).