[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZuOSy3ITxJ7tkMnl@archie.me>
Date: Fri, 13 Sep 2024 08:18:03 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Nicolin Chen <nicolinc@...dia.com>, jgg@...dia.com,
kevin.tian@...el.com
Cc: corbet@....net, iommu@...ts.linux.dev, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, yi.l.liu@...el.com,
eric.auger@...hat.com, shameerali.kolothum.thodi@...wei.com,
smostafa@...gle.com, baolu.lu@...ux.intel.com
Subject: Re: [PATCH v2] Documentation: userspace-api: iommufd: Update
HWPT_PAGING and HWPT_NESTED
On Wed, Sep 11, 2024 at 07:15:03PM -0700, Nicolin Chen wrote:
> +- IOMMUFD_OBJ_HWPT_NESTED, representing an actual hardware I/O page table
> + (i.e. a single struct iommu_domain) managed by user space (e.g. guest OS).
> + "NESTED" indicates that this type of HWPT should be linked to an HWPT_PAGING.
> + It also indicates that it is backed by an iommu_domain that has a type of
> + IOMMU_DOMAIN_NESTED. This must be a stage-1 domain for a device running in
> + the user space (e.g. in a guest VM enabling the IOMMU nested translation
> + feature.) So it must be created with a given nesting parent stage-2 domain
"As such, it must be ..."
> + to associate to. This nested stage-1 page table managed by the user space
> + usually has mappings from guest-level I/O virtual addresses to guest-level
> + physical addresses.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists