From: Alexey Kardashevskiy <aik@amd.com>
To: Nicolin Chen <nicolinc@nvidia.com>,
jgg@nvidia.com, kevin.tian@intel.com, will@kernel.org
Cc: joro@8bytes.org, suravee.suthikulpanit@amd.com,
robin.murphy@arm.com, dwmw2@infradead.org,
baolu.lu@linux.intel.com, shuah@kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, eric.auger@redhat.com,
jean-philippe@linaro.org, mdf@kernel.org, mshavit@google.com,
shameerali.kolothum.thodi@huawei.com, smostafa@google.com,
yi.l.liu@intel.com, zhangfei.gao@linaro.org,
patches@lists.linux.dev
Subject: Re: [PATCH v4 00/14] iommufd: Add vIOMMU infrastructure (Part-2: vDEVICE)
Date: Fri, 25 Oct 2024 15:54:44 +1100 [thread overview]
Message-ID: <98a0e135-4f9b-4a2e-94b5-f1a830a49f19@amd.com> (raw)
In-Reply-To: <cover.1729555967.git.nicolinc@nvidia.com>
On 22/10/24 11:20, Nicolin Chen wrote:
> Following the previous vIOMMU series, this adds another vDEVICE structure,
> representing the association from an iommufd_device to an iommufd_viommu.
> This gives the whole architecture a new "v" layer:
> _______________________________________________________________________
> | iommufd (with vIOMMU/vDEVICE) |
> | _____________ _____________ |
> | | | | | |
> | |----------------| vIOMMU |<---| vDEVICE |<------| |
> | | | | |_____________| | |
> | | ______ | | _____________ ___|____ |
> | | | | | | | | | | |
> | | | IOAS |<---|(HWPT_PAGING)|<---| HWPT_NESTED |<--| DEVICE | |
> | | |______| |_____________| |_____________| |________| |
> |______|________|______________|__________________|_______________|_____|
> | | | | |
> ______v_____ | ______v_____ ______v_____ ___v__
> | struct | | PFN | (paging) | | (nested) | |struct|
> |iommu_device| |------>|iommu_domain|<----|iommu_domain|<----|device|
> |____________| storage|____________| |____________| |______|
>
> This vDEVICE object is used to collect and store all vIOMMU-related device
> information/attributes in a VM. As an initial series for vDEVICE, add only
> the virt_id to the vDEVICE, which is a vIOMMU specific device ID in a VM:
> e.g. vSID of ARM SMMUv3, vDeviceID of AMD IOMMU, and vID of Intel VT-d to
> a Context Table. This virt_id helps IOMMU drivers to link the vID to a pID
> of the device against the physical IOMMU instance. This is essential for a
> vIOMMU-based invalidation, where the request contains a device's vID for a
> device cache flush, e.g. ATC invalidation.
>
> Therefore, with this vDEVICE object, support a vIOMMU-based invalidation,
> by reusing IOMMUFD_CMD_HWPT_INVALIDATE for a vIOMMU object to flush cache
> with a given driver data.
>
> As for the implementation of the series, add driver support in ARM SMMUv3
> for a real world use case.
>
> This series is on Github:
> https://github.com/nicolinc/iommufd/commits/iommufd_viommu_p2-v4
>
> For testing, try this "with-rmr" branch:
> https://github.com/nicolinc/iommufd/commits/iommufd_viommu_p2-v4-with-rmr
Is there any real example of a .vdevice_alloc hook, besides the
selftests? It is not in iommufd_viommu_p2-v4-with-rmr, hence the
question. I am trying to sketch something with this new machinery and
less guessing would be nice. Thanks,
> Paring QEMU branch for testing:
> https://github.com/nicolinc/qemu/commits/wip/for_iommufd_viommu_p2-v4
>
> Changelog
> v4
> * Added missing brackets in switch-case
> * Fixed the unreleased idev refcount issue
> * Reworked the iommufd_vdevice_alloc allocator
> * Dropped support for IOMMU_VIOMMU_TYPE_DEFAULT
> * Added missing TEST_LENGTH and fail_nth coverages
> * Added a verification to the driver-allocated vDEVICE object
> * Added an iommufd_vdevice_abort for a missing mutex protection
> * Added a u64 structure arm_vsmmu_invalidation_cmd for user command
> conversion
> v3
> https://lore.kernel.org/all/cover.1728491532.git.nicolinc@nvidia.com/
> * Added Jason's Reviewed-by
> * Split this invalidation part out of the part-1 series
> * Repurposed VDEV_ID ioctl to a wider vDEVICE structure and ioctl
> * Reduced viommu_api functions by allowing drivers to access viommu
> and vdevice structure directly
> * Dropped vdevs_rwsem by using xa_lock instead
> * Dropped arm_smmu_cache_invalidate_user
> v2
> https://lore.kernel.org/all/cover.1724776335.git.nicolinc@nvidia.com/
> * Limited vdev_id to one per idev
> * Added a rw_sem to protect the vdev_id list
> * Reworked driver-level APIs with proper lockings
> * Added a new viommu_api file for IOMMUFD_DRIVER config
> * Dropped useless iommu_dev point from the viommu structure
> * Added missing index numnbers to new types in the uAPI header
> * Dropped IOMMU_VIOMMU_INVALIDATE uAPI; Instead, reuse the HWPT one
> * Reworked mock_viommu_cache_invalidate() using the new iommu helper
> * Reordered details of set/unset_vdev_id handlers for proper lockings
> v1
> https://lore.kernel.org/all/cover.1723061377.git.nicolinc@nvidia.com/
>
> Thanks!
> Nicolin
>
> Jason Gunthorpe (2):
> iommu: Add iommu_copy_struct_from_full_user_array helper
> iommu/arm-smmu-v3: Allow ATS for IOMMU_DOMAIN_NESTED
>
> Nicolin Chen (12):
> iommufd/viommu: Introduce IOMMUFD_OBJ_VDEVICE and its related struct
> iommufd/viommu: Add IOMMU_VDEVICE_ALLOC ioctl
> iommufd/selftest: Add IOMMU_VDEVICE_ALLOC test coverage
> iommu/viommu: Add cache_invalidate to iommufd_viommu_ops
> iommufd/hw_pagetable: Enforce cache invalidation op on vIOMMU-based
> hwpt_nested
> iommufd: Allow hwpt_id to carry viommu_id for IOMMU_HWPT_INVALIDATE
> iommufd/viommu: Add vdev_to_dev helper
> iommufd/selftest: Add mock_viommu_cache_invalidate
> iommufd/selftest: Add IOMMU_TEST_OP_DEV_CHECK_CACHE test command
> iommufd/selftest: Add vIOMMU coverage for IOMMU_HWPT_INVALIDATE ioctl
> Documentation: userspace-api: iommufd: Update vDEVICE
> iommu/arm-smmu-v3: Add arm_vsmmu_cache_invalidate
>
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.h | 9 +-
> drivers/iommu/iommufd/iommufd_private.h | 12 ++
> drivers/iommu/iommufd/iommufd_test.h | 30 +++
> include/linux/iommu.h | 49 ++++-
> include/linux/iommufd.h | 50 +++++
> include/uapi/linux/iommufd.h | 61 +++++-
> tools/testing/selftests/iommu/iommufd_utils.h | 83 +++++++
> .../arm/arm-smmu-v3/arm-smmu-v3-iommufd.c | 162 +++++++++++++-
> drivers/iommu/arm/arm-smmu-v3/arm-smmu-v3.c | 32 ++-
> drivers/iommu/iommufd/device.c | 11 +
> drivers/iommu/iommufd/driver.c | 7 +
> drivers/iommu/iommufd/hw_pagetable.c | 36 +++-
> drivers/iommu/iommufd/main.c | 7 +
> drivers/iommu/iommufd/selftest.c | 115 +++++++++-
> drivers/iommu/iommufd/viommu.c | 108 ++++++++++
> tools/testing/selftests/iommu/iommufd.c | 204 +++++++++++++++++-
> .../selftests/iommu/iommufd_fail_nth.c | 4 +
> Documentation/userspace-api/iommufd.rst | 41 +++-
> 18 files changed, 983 insertions(+), 38 deletions(-)
>
--
Alexey
next prev parent reply other threads:[~2024-10-25 4:54 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 0:20 Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 01/14] iommufd/viommu: Introduce IOMMUFD_OBJ_VDEVICE and its related struct Nicolin Chen
2024-10-25 3:37 ` Nicolin Chen
2024-10-25 7:53 ` Alexey Kardashevskiy
2024-10-25 13:20 ` Jason Gunthorpe
2024-10-25 16:39 ` Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 02/14] iommufd/viommu: Add IOMMU_VDEVICE_ALLOC ioctl Nicolin Chen
2024-10-22 3:40 ` Baolu Lu
2024-10-22 4:40 ` Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 03/14] iommufd/selftest: Add IOMMU_VDEVICE_ALLOC test coverage Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 04/14] iommu/viommu: Add cache_invalidate to iommufd_viommu_ops Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 05/14] iommufd/hw_pagetable: Enforce cache invalidation op on vIOMMU-based hwpt_nested Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 06/14] iommufd: Allow hwpt_id to carry viommu_id for IOMMU_HWPT_INVALIDATE Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 07/14] iommu: Add iommu_copy_struct_from_full_user_array helper Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 08/14] iommufd/viommu: Add vdev_to_dev helper Nicolin Chen
2024-10-25 3:39 ` Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 09/14] iommufd/selftest: Add mock_viommu_cache_invalidate Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 10/14] iommufd/selftest: Add IOMMU_TEST_OP_DEV_CHECK_CACHE test command Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 11/14] iommufd/selftest: Add vIOMMU coverage for IOMMU_HWPT_INVALIDATE ioctl Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 12/14] Documentation: userspace-api: iommufd: Update vDEVICE Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 13/14] iommu/arm-smmu-v3: Add arm_vsmmu_cache_invalidate Nicolin Chen
2024-10-22 0:20 ` [PATCH v4 14/14] iommu/arm-smmu-v3: Allow ATS for IOMMU_DOMAIN_NESTED Nicolin Chen
2024-10-25 4:54 ` Alexey Kardashevskiy [this message]
2024-10-25 4:59 ` [PATCH v4 00/14] iommufd: Add vIOMMU infrastructure (Part-2: vDEVICE) Nicolin Chen
2024-10-25 5:32 ` Alexey Kardashevskiy
2024-10-25 5:41 ` Nicolin Chen
2024-10-25 5:58 ` Alexey Kardashevskiy
2024-10-25 6:14 ` Nicolin Chen
2024-10-25 13:29 ` Jason Gunthorpe
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=98a0e135-4f9b-4a2e-94b5-f1a830a49f19@amd.com \
--to=aik@amd.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.com \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shuah@kernel.org \
--cc=smostafa@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
--cc=zhangfei.gao@linaro.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
all inboxes | Powered by JetHome®