From: Yi Liu <yi.l.liu@intel.com>
To: Zhenzhong Duan <zhenzhong.duan@intel.com>, <qemu-devel@nongnu.org>
Cc: <mst@redhat.com>, <jasowang@redhat.com>, <peterx@redhat.com>,
<clement.mathieu--drif@eviden.com>
Subject: Re: [PATCH v3 2/3] intel_iommu: Reset pasid cache when system level reset
Date: Mon, 20 Oct 2025 20:44:42 +0800 [thread overview]
Message-ID: <6c0f8cd8-543a-4512-827b-57a49cfd53f5@intel.com> (raw)
In-Reply-To: <20251017093602.525338-3-zhenzhong.duan@intel.com>
On 2025/10/17 17:36, Zhenzhong Duan wrote:
> Reset pasid cache when system level reset. Currently we don't have any
> device supporting PASID yet. So all are PASID_0, its vtd_as is allocated
> by PCI system and never removed, just mark pasid cache invalid.
>
> Signed-off-by: Yi Liu <yi.l.liu@intel.com>
> Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
> ---
> hw/i386/intel_iommu.c | 16 ++++++++++++++++
> hw/i386/trace-events | 1 +
> 2 files changed, 17 insertions(+)
Reviewed-by: Yi Liu <yi.l.liu@intel.com>
> diff --git a/hw/i386/intel_iommu.c b/hw/i386/intel_iommu.c
> index c47f13b659..07bc0a749c 100644
> --- a/hw/i386/intel_iommu.c
> +++ b/hw/i386/intel_iommu.c
> @@ -87,6 +87,21 @@ struct vtd_iotlb_key {
> static void vtd_address_space_refresh_all(IntelIOMMUState *s);
> static void vtd_address_space_unmap(VTDAddressSpace *as, IOMMUNotifier *n);
>
> +static void vtd_pasid_cache_reset_locked(IntelIOMMUState *s)
> +{
> + VTDAddressSpace *vtd_as;
> + GHashTableIter as_it;
> +
> + trace_vtd_pasid_cache_reset();
> +
> + g_hash_table_iter_init(&as_it, s->vtd_address_spaces);
> + while (g_hash_table_iter_next(&as_it, NULL, (void **)&vtd_as)) {
> + VTDPASIDCacheEntry *pc_entry = &vtd_as->pasid_cache_entry;
> + pc_entry->valid = false;
> + }
> +}
> +
> +
> static void vtd_define_quad(IntelIOMMUState *s, hwaddr addr, uint64_t val,
> uint64_t wmask, uint64_t w1cmask)
> {
> @@ -381,6 +396,7 @@ static void vtd_reset_caches(IntelIOMMUState *s)
> vtd_iommu_lock(s);
> vtd_reset_iotlb_locked(s);
> vtd_reset_context_cache_locked(s);
> + vtd_pasid_cache_reset_locked(s);
> vtd_iommu_unlock(s);
> }
>
> diff --git a/hw/i386/trace-events b/hw/i386/trace-events
> index 298addb24d..b704f4f90c 100644
> --- a/hw/i386/trace-events
> +++ b/hw/i386/trace-events
> @@ -24,6 +24,7 @@ vtd_inv_qi_head(uint16_t head) "read head %d"
> vtd_inv_qi_tail(uint16_t head) "write tail %d"
> vtd_inv_qi_fetch(void) ""
> vtd_context_cache_reset(void) ""
> +vtd_pasid_cache_reset(void) ""
> vtd_inv_desc_pasid_cache_gsi(void) ""
> vtd_inv_desc_pasid_cache_dsi(uint16_t domain) "Domain selective PC invalidation domain 0x%"PRIx16
> vtd_inv_desc_pasid_cache_psi(uint16_t domain, uint32_t pasid) "PASID selective PC invalidation domain 0x%"PRIx16" pasid 0x%"PRIx32
next prev parent reply other threads:[~2025-10-20 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-17 9:35 [PATCH v3 0/3] Fix DMA failure when there is domain switch in guest Zhenzhong Duan
2025-10-17 9:36 ` [PATCH v3 1/3] intel_iommu: Handle PASID cache invalidation Zhenzhong Duan
2025-10-17 9:36 ` [PATCH v3 2/3] intel_iommu: Reset pasid cache when system level reset Zhenzhong Duan
2025-10-20 12:44 ` Yi Liu [this message]
2025-10-17 9:36 ` [PATCH v3 3/3] intel_iommu: Fix DMA failure when guest switches IOMMU domain Zhenzhong Duan
2025-10-20 12:46 ` Yi Liu
2025-10-21 3:04 ` Duan, Zhenzhong
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=6c0f8cd8-543a-4512-827b-57a49cfd53f5@intel.com \
--to=yi.l.liu@intel.com \
--cc=clement.mathieu--drif@eviden.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhenzhong.duan@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 NNTP newsgroup(s).