From: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
To: <linux-kernel@vger.kernel.org>, <iommu@lists.linux.dev>,
<joro@8bytes.org>, <jgg@nvidia.com>
Cc: <yi.l.liu@intel.com>, <kevin.tian@intel.com>,
<nicolinc@nvidia.com>, <eric.auger@redhat.com>,
<vasant.hegde@amd.com>, <jon.grimm@amd.com>,
<santosh.shukla@amd.com>, <Dhaval.Giani@amd.com>,
<pandoh@google.com>, <loganodell@google.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: [RFCv2 PATCH 0/7] iommu/amd: Introduce hardware info reporting and nested translation support
Date: Thu, 11 Jan 2024 18:06:39 -0600 [thread overview]
Message-ID: <20240112000646.98001-1-suravee.suthikulpanit@amd.com> (raw)
OVERVIEW
--------
This is the first part of multi-part series to introduce the AMD IOMMU
nested translation support with Hardware-virtualized IOMMU (HW-vIOMMU),
which allows user-space to take adventage of hardware accelerated
AMD IOMMU in the guest.
The part 1 introduces AMD IOMMU hardware info reporting support via
the ioctl IOMMU_GET_HW_INFO with enum IOMMU_HW_INFO_TYPE_AMD. This allows
hypervisor to communicate the supported capabilities to user-space.
For example, this information can be used by QEMU to populate EFR and EFR2
field in the guest IVRS table when building guest ACPI table.
In addition, this series introduces nested translation support for the
AMD IOMMU v2 page table (stage-1) via the IOMMUFD nesting infrastructure.
This allows User-space to set up the v2 page table and communicate
information via the struct iommu_hwpt_amd_v2 with enum
IOMMU_HWPT_DATA_AMD_V2.
This series is based on top of:
* Linux v6.7-rc5
* Series [PATCH v2 0/9] Improve TLB invalidation logic
(Currently queued in https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git/log/?h=next)
* Series [PATCH v4 00/16] iommu/amd: SVA Support (part 3) - refactor support for GCR3 table
(https://lore.kernel.org/all/20231212085224.6985-1-vasant.hegde@amd.com/)
GITHUB
------
[1] https://github.com/AMDESE/linux/tree/iommu_sva_part3_v4_v6.7_rc5-amd_nesting_rfc_v2.1
(Complete code for the part 1 of this series)
[2] https://github.com/AMDESE/linux/tree/wip/iommu_sva_part3_v4_v6.7_rc5-amd_viommu_20240112.1
(WIP for Linux AMD Hw-vIOMMU support)
CHANGES
-------
* Patch 1 : New
* Patch 2 : New
* Patch 4 : Modifies the amd_iommu_build_efr to also check the advertised capabilities against
the current hardware (per Kevin)
* Patch 4 : Also add reference to IOMMU spec in the comment (per Jason)
* Patch 5 : Removes gid, iommu_id, gdev_id (per Jason), and introduce the struct flags and giov tracking.
* Patch 6,7 : Separate logic for nested domain allocation and attachment into two patches (per Jason).
HISTORY
-------
* [RFC PATCH 0/6] iommu/amd: Introduce hardware info reporting and nested translation support
(https://lore.kernel.org/linux-iommu/20231212160139.174229-1-suravee.suthikulpanit@amd.com/)
* [RFC PATCH 00/21] iommu/amd: Introduce support for HW accelerated vIOMMU w/ nested page table
(https://lore.kernel.org/lkml/20230621235508.113949-1-suravee.suthikulpanit@amd.com/)
Thank you,
Suravee
Suravee Suthikulpanit (7):
iommu/amd: Introduce struct gcr3_tbl_info.giov
iommu/amd: Refactor set_dte_entry
iommu/amd: Update PASID, GATS, and GLX feature related macros
iommu/amd: Add support for hw_info for iommu capability query
iommufd: Introduce data struct for AMD nested domain allocation
iommu/amd: Add nested domain allocation support
iommu/amd: Add nested domain attach/detach support
drivers/iommu/amd/Makefile | 2 +-
drivers/iommu/amd/amd_iommu.h | 14 +-
drivers/iommu/amd/amd_iommu_types.h | 20 +-
drivers/iommu/amd/init.c | 8 +-
drivers/iommu/amd/iommu.c | 298 ++++++++++++++++++++++------
drivers/iommu/amd/nested.c | 75 +++++++
include/uapi/linux/iommufd.h | 45 +++++
7 files changed, 387 insertions(+), 75 deletions(-)
create mode 100644 drivers/iommu/amd/nested.c
--
2.34.1
next reply other threads:[~2024-01-12 0:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 0:06 Suravee Suthikulpanit [this message]
2024-01-12 0:06 ` [RFCv2 PATCH 1/7] iommu/amd: Introduce struct gcr3_tbl_info.giov Suravee Suthikulpanit
2024-03-08 13:48 ` Jason Gunthorpe
2024-01-12 0:06 ` [RFCv2 PATCH 2/7] iommu/amd: Refactor set_dte_entry Suravee Suthikulpanit
2024-01-22 8:39 ` Tian, Kevin
2024-03-08 13:51 ` Jason Gunthorpe
2024-01-12 0:06 ` [RFCv2 PATCH 3/7] iommu/amd: Update PASID, GATS, and GLX feature related macros Suravee Suthikulpanit
2024-03-08 13:55 ` Jason Gunthorpe
2024-01-12 0:06 ` [RFCv2 PATCH 4/7] iommu/amd: Add support for hw_info for iommu capability query Suravee Suthikulpanit
2024-03-08 13:57 ` Jason Gunthorpe
2024-01-12 0:06 ` [RFCv2 PATCH 5/7] iommufd: Introduce data struct for AMD nested domain allocation Suravee Suthikulpanit
2024-01-22 8:46 ` Tian, Kevin
2024-03-08 13:58 ` Jason Gunthorpe
2024-01-12 0:06 ` [RFCv2 PATCH 6/7] iommu/amd: Add nested domain allocation support Suravee Suthikulpanit
2024-01-22 8:52 ` Tian, Kevin
2024-03-08 14:04 ` Jason Gunthorpe
2024-01-12 0:06 ` [RFCv2 PATCH 7/7] iommu/amd: Add nested domain attach/detach support Suravee Suthikulpanit
2024-01-22 8:56 ` Tian, Kevin
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=20240112000646.98001-1-suravee.suthikulpanit@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=Dhaval.Giani@amd.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loganodell@google.com \
--cc=nicolinc@nvidia.com \
--cc=pandoh@google.com \
--cc=santosh.shukla@amd.com \
--cc=vasant.hegde@amd.com \
--cc=yi.l.liu@intel.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).