From: Sairaj Kodilkar <sarunkod@amd.com>
To: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
<qemu-devel@nongnu.org>
Cc: <pbonzini@redhat.com>, <richard.henderson@linaro.org>,
<eduardo@habkost.net>, <peterx@redhat.com>, <david@redhat.com>,
<philmd@linaro.org>, <mst@redhat.com>,
<marcel.apfelbaum@gmail.com>, <alex.williamson@redhat.com>,
<vasant.hegde@amd.com>, <suravee.suthikulpanit@amd.com>,
<santosh.shukla@amd.com>, <Wei.Huang2@amd.com>,
<joao.m.martins@oracle.com>, <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH 08/18] amd_iommu: Helper to decode size of page invalidation command
Date: Tue, 22 Apr 2025 17:56:37 +0530 [thread overview]
Message-ID: <36a69911-ff85-47e4-a34d-cf5e934d85da@amd.com> (raw)
In-Reply-To: <20250414020253.443831-9-alejandro.j.jimenez@oracle.com>
On 4/14/2025 7:32 AM, Alejandro Jimenez wrote:
> The size of the region to invalidate depends on the S bit and address
> encoded in the command. Add a helper to extract this information, which
> will be used to sync shadow page tables in upcoming changes.
>
> Signed-off-by: Alejandro Jimenez <alejandro.j.jimenez@oracle.com>
> ---
> hw/i386/amd_iommu.c | 34 ++++++++++++++++++++++++++++++++++
> hw/i386/amd_iommu.h | 4 ++++
> 2 files changed, 38 insertions(+)
>
> diff --git a/hw/i386/amd_iommu.c b/hw/i386/amd_iommu.c
> index 5f55be1f4d36..0af873b66a31 100644
> --- a/hw/i386/amd_iommu.c
> +++ b/hw/i386/amd_iommu.c
> @@ -481,6 +481,40 @@ static gboolean amdvi_iotlb_remove_by_domid(gpointer key, gpointer value,
> return entry->domid == domid;
> }
>
> +/*
> + * Helper to decode the size of the range to invalidate encoded in the
> + * INVALIDATE_IOMMU_PAGES Command format.
> + * The size of the region to invalidate depends on the S bit and address.
> + * S bit value:
> + * 0 : Invalidation size is 4 Kbytes.
> + * 1 : Invalidation size is determined by first zero bit in the address
> + * starting from Address[12].
> + *
> + * In the AMD IOMMU Linux driver, an invalidation command with address
> + * ((1 << 63) - 1) is sent when intending to clear the entire cache.
> + * However, Table 14: Example Page Size Encodings shows that an address of
> + * ((1ULL << 51) - 1) encodes the entire cache, so effectively any address with
> + * first zero at bit 51 or larger is a request to invalidate the entire address
> + * space.
> + */
> +static uint64_t __attribute__((unused))
> +amdvi_decode_invalidation_size(hwaddr addr, uint16_t flags)
> +{
> + uint64_t size = AMDVI_PAGE_SIZE;
> + uint8_t fzbit = 0;
> +
> + if (flags & AMDVI_CMD_INVAL_IOMMU_PAGES_S) {
> + fzbit = cto64(addr | 0xFFF);
> +
> + if (fzbit >= 51 || !addr) {
I am skeptical about the condition addr == 0 (!addr)
Consider the case where user wants to invalidate 8K size page, starting
from address 0. It'll cause address field to be 0, right ? If so, then
we should invalidate only 8K page not the entire address range.
Am I missing something here ?
Regards
Sairaj
> + size = AMDVI_INV_ALL_PAGES;
> + } else {> + size = 1ULL << (fzbit + 1);
> + }
> + }
> + return size;
> +}
> +
> /* we don't have devid - we can't remove pages by address */
> static void amdvi_inval_pages(AMDVIState *s, uint64_t *cmd)
> {
> diff --git a/hw/i386/amd_iommu.h b/hw/i386/amd_iommu.h
> index e12ecade4baa..c89e7dc9947d 100644
> --- a/hw/i386/amd_iommu.h
> +++ b/hw/i386/amd_iommu.h
> @@ -123,6 +123,10 @@
> #define AMDVI_CMD_COMPLETE_PPR_REQUEST 0x07
> #define AMDVI_CMD_INVAL_AMDVI_ALL 0x08
>
> +
> +#define AMDVI_CMD_INVAL_IOMMU_PAGES_S (1ULL << 0)
> +#define AMDVI_INV_ALL_PAGES (1ULL << 52)
> +
> #define AMDVI_DEVTAB_ENTRY_SIZE 32
>
> /* Device table entry bits 0:63 */
next prev parent reply other threads:[~2025-04-22 12:27 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 2:02 [PATCH 00/18] AMD vIOMMU: DMA remapping support for VFIO devices Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 01/18] memory: Adjust event ranges to fit within notifier boundaries Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 02/18] amd_iommu: Add helper function to extract the DTE Alejandro Jimenez
2025-04-16 11:36 ` Sairaj Kodilkar
2025-04-16 13:29 ` Alejandro Jimenez
2025-04-16 18:50 ` Michael S. Tsirkin
2025-04-16 22:37 ` Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 03/18] amd_iommu: Add support for IOMMU notifier Alejandro Jimenez
2025-04-16 12:14 ` Sairaj Kodilkar
2025-04-16 22:17 ` Alejandro Jimenez
2025-04-17 10:19 ` Sairaj Kodilkar
2025-04-17 16:21 ` Alejandro Jimenez
2025-04-17 16:34 ` Michael S. Tsirkin
2025-04-18 6:33 ` Sairaj Kodilkar
2025-04-14 2:02 ` [PATCH 04/18] amd_iommu: Unmap all address spaces under the AMD IOMMU on reset Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 05/18] amd_iommu: Toggle memory regions based on address translation mode Alejandro Jimenez
2025-04-22 12:17 ` Sairaj Kodilkar
2025-04-28 21:10 ` Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 06/18] amd_iommu: Set all address spaces to default translation mode on reset Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 07/18] amd_iommu: Return an error when unable to read PTE from guest memory Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 08/18] amd_iommu: Helper to decode size of page invalidation command Alejandro Jimenez
2025-04-22 12:26 ` Sairaj Kodilkar [this message]
2025-04-28 21:16 ` Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 09/18] amd_iommu: Add helpers to walk AMD v1 Page Table format Alejandro Jimenez
2025-04-17 12:40 ` CLEMENT MATHIEU--DRIF
2025-04-17 15:27 ` Alejandro Jimenez
2025-04-18 5:30 ` CLEMENT MATHIEU--DRIF
2025-04-23 6:28 ` Sairaj Kodilkar
2025-04-14 2:02 ` [PATCH 10/18] amd_iommu: Add a page walker to sync shadow page tables on invalidation Alejandro Jimenez
2025-04-17 15:14 ` Ethan MILON
2025-04-17 15:45 ` Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 11/18] amd_iommu: Sync shadow page tables on page invalidation Alejandro Jimenez
2025-04-22 12:38 ` Sairaj Kodilkar
2025-04-22 12:38 ` Sairaj Kodilkar
2025-04-29 19:47 ` Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 12/18] amd_iommu: Add replay callback Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 13/18] amd_iommu: Invalidate address translations on INVALIDATE_IOMMU_ALL Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 14/18] amd_iommu: Toggle address translation on device table entry invalidation Alejandro Jimenez
2025-04-22 12:48 ` Sairaj Kodilkar
2025-04-29 20:45 ` Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 15/18] amd_iommu: Use iova_tree records to determine large page size on UNMAP Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 16/18] amd_iommu: Do not assume passthrough translation when DTE[TV]=0 Alejandro Jimenez
2025-04-23 6:06 ` Sairaj Kodilkar
2025-04-14 2:02 ` [PATCH 17/18] amd_iommu: Refactor amdvi_page_walk() to use common code for page walk Alejandro Jimenez
2025-04-14 2:02 ` [PATCH 18/18] amd_iommu: Do not emit I/O page fault events during replay() Alejandro Jimenez
2025-04-23 6:18 ` Sairaj Kodilkar
2025-04-23 10:45 ` [PATCH 00/18] AMD vIOMMU: DMA remapping support for VFIO devices Sairaj Kodilkar
2025-04-23 10:56 ` Sairaj Kodilkar
2025-04-24 11:49 ` Joao Martins
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=36a69911-ff85-47e4-a34d-cf5e934d85da@amd.com \
--to=sarunkod@amd.com \
--cc=Wei.Huang2@amd.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=alex.williamson@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=joao.m.martins@oracle.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=santosh.shukla@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=vasant.hegde@amd.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 NNTP newsgroup(s).