linux-kernel - Re: [PATCH v2 15/22] Documentation: userspace-api: iommufd: Update vCMDQ

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aA-RQwyTS1m4CuPw@archie.me>
Date: Mon, 28 Apr 2025 21:31:31 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Nicolin Chen <nicolinc@...dia.com>, jgg@...dia.com,
	kevin.tian@...el.com, corbet@....net, will@...nel.org
Cc: robin.murphy@....com, joro@...tes.org, thierry.reding@...il.com,
	vdumpa@...dia.com, jonathanh@...dia.com, shuah@...nel.org,
	jsnitsel@...hat.com, nathan@...nel.org, peterz@...radead.org,
	yi.l.liu@...el.com, mshavit@...gle.com, praan@...gle.com,
	zhangzekun11@...wei.com, iommu@...ts.linux.dev,
	linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-tegra@...r.kernel.org,
	linux-kselftest@...r.kernel.org, patches@...ts.linux.dev,
	mochs@...dia.com, alok.a.tiwari@...cle.com, vasant.hegde@....com
Subject: Re: [PATCH v2 15/22] Documentation: userspace-api: iommufd: Update
 vCMDQ

On Fri, Apr 25, 2025 at 10:58:10PM -0700, Nicolin Chen wrote:
> +- IOMMUFD_OBJ_VCMDQ, representing a hardware queue as a subset of a vIOMMU's
> +  virtualization feature for a VM to directly execute guest-issued commands to
> +  invalidate HW cache entries holding the mappings or translations of a guest-
> +  owned stage-1 page table. Along with this queue object, iommufd provides the
> +  user space an mmap interface for VMM to mmap a physical MMIO region from the
> +  host physical address space to a guest physical address space, to exclusively
> +  control the allocated vCMDQ HW. Thus, when allocating a vCMDQ, the VMM must
> +  request a pair of VMA info (vm_pgoff/size) for a later mmap call. The length
> +  argument of an mmap call could be smaller than the given size for a paritial
> +  mmap, but the given vm_pgoff (as the addr argument of the mmap call) should
"... partial mmap, ..."
> +  never be offsetted, which also implies that the mmap will always start from
> +  the beginning of the physical MMIO region.
> +
 
Thanks.

-- 
An old man doll... just what I always wanted! - Clara

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)