From: Chao Gao <chao.gao@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, Wei.Huang2@amd.com, dgilbert@redhat.com,
peterx@redhat.com, qemu-devel@nongnu.org, Sriyash.Caculo@amd.com,
pbonzini@redhat.com
Subject: Re: [PATCH 0/3] Disable vhost device IOTLB is IOMMU is not enabled
Date: Wed, 4 Aug 2021 13:57:04 +0800 [thread overview]
Message-ID: <20210804055703.GA5925@gao-cwp> (raw)
In-Reply-To: <20210804034803.1644-1-jasowang@redhat.com>
On Wed, Aug 04, 2021 at 11:48:00AM +0800, Jason Wang wrote:
>Hi:
>
>We currently try to enable device IOTLB when iommu_platform is
>set. This may lead unnecessary trasnsactions between qemu and vhost
>when vIOMMU is not used (which is the typical case for the encrypted
>VM).
>
>So patch tries to use transport specific method to detect the enalbing
>of vIOMMU and enable the device IOTLB only if vIOMMU is enalbed.
>
>Please review.
Tested-by: Chao Gao <chao.gao@intel.com>
Tested with TDX; this series fixes the performance issue we saw in a TD
when vhost was enabled.
Thanks
Chao
>
>Thanks
>
>Jason Wang (3):
> virtio-bus: introduce iommu_enabled()
> virtio-pci: implement iommu_enabled()
> vhost: correctly detect the enabling IOMMU
>
> hw/virtio/vhost.c | 2 +-
> hw/virtio/virtio-bus.c | 14 ++++++++++++++
> hw/virtio/virtio-pci.c | 14 ++++++++++++++
> include/hw/virtio/virtio-bus.h | 4 +++-
> 4 files changed, 32 insertions(+), 2 deletions(-)
>
>--
>2.25.1
>
next prev parent reply other threads:[~2021-08-04 5:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 3:48 [PATCH 0/3] Disable vhost device IOTLB is IOMMU is not enabled Jason Wang
2021-08-04 3:48 ` [PATCH 1/3] virtio-bus: introduce iommu_enabled() Jason Wang
2021-08-04 3:48 ` [PATCH 2/3] virtio-pci: implement iommu_enabled() Jason Wang
2021-08-04 3:48 ` [PATCH 3/3] vhost: correctly detect the enabling IOMMU Jason Wang
2021-08-04 5:57 ` Chao Gao [this message]
2021-08-04 16:08 ` [PATCH 0/3] Disable vhost device IOTLB is IOMMU is not enabled Peter Xu
2021-08-05 1:46 ` Jason Wang
2021-08-05 3:08 ` Peter Xu
2021-08-05 7:26 ` Caculo, Sriyash
2021-09-02 5:46 ` 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=20210804055703.GA5925@gao-cwp \
--to=chao.gao@intel.com \
--cc=Sriyash.Caculo@amd.com \
--cc=Wei.Huang2@amd.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).