From: Teddy Astie <teddy.astie@vates.tech>
To: xen-devel@lists.xenproject.org
Cc: Teddy Astie <teddy.astie@vates.tech>
Subject: [XEN PATCH 0/3] x86/iommu: Drop IOMMU support when cpu doesn't support cx16.
Date: Thu, 21 Mar 2024 10:28:25 +0000 [thread overview]
Message-ID: <cover.1711016106.git.teddy.astie@vates.tech> (raw)
All hardware that supports VT-d/AMD-Vi that exists also supports cx16 (aside specifically crafted virtual machines).
Some IOMMU code paths in Xen consider cases where VT-d/AMD-Vi is supported while cx16 isn't, those paths may be bugged and are barely tested, dead code in practice.
Consider disabling IOMMU in case we have IOMMU hardware but no cx16, then cleanup no-cx16 handling logic from VT-d and AMD-Vi drivers.
Teddy Astie (3):
VT-d: Disable IOMMU if cx16 isn't supported
AMD-Vi: Disable IOMMU if cx16 isn't supported
VT-d: Cleanup MAP_SINGLE_DEVICE and related dead code.
xen/drivers/passthrough/amd/iommu_map.c | 43 ++++------
xen/drivers/passthrough/amd/pci_amd_iommu.c | 6 ++
xen/drivers/passthrough/vtd/intremap.c | 67 ++++-----------
xen/drivers/passthrough/vtd/iommu.c | 92 +++++++--------------
xen/drivers/passthrough/vtd/vtd.h | 5 +-
5 files changed, 67 insertions(+), 146 deletions(-)
--
2.44.0
Teddy Astie | Vates XCP-ng Intern
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
next reply other threads:[~2024-03-21 10:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 10:28 Teddy Astie [this message]
2024-03-21 10:28 ` [XEN PATCH 1/3] VT-d: Disable IOMMU if cx16 isn't supported Teddy Astie
2024-03-21 10:51 ` Jan Beulich
2024-03-21 10:28 ` [XEN PATCH 2/3] AMD-Vi: " Teddy Astie
2024-03-21 10:41 ` Jan Beulich
2024-03-21 10:28 ` [XEN PATCH 3/3] VT-d: Cleanup MAP_SINGLE_DEVICE and related dead code Teddy Astie
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=cover.1711016106.git.teddy.astie@vates.tech \
--to=teddy.astie@vates.tech \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.