diff options
author | Zhenzhong Duan <zhenzhong.duan@intel.com> | 2024-12-12 16:37:47 +0800 |
---|---|---|
committer | Michael S. Tsirkin <mst@redhat.com> | 2025-01-15 13:06:20 -0500 |
commit | 16d4e418e98feeb53f28d17eeffb198fe0fd6f22 (patch) | |
tree | 185eded20f115f7604306588004aa0557ad4954d /rust | |
parent | 65c4f0999991f6321d6a369fa56c81c57c5b87ad (diff) | |
download | qemu-16d4e418e98feeb53f28d17eeffb198fe0fd6f22.zip qemu-16d4e418e98feeb53f28d17eeffb198fe0fd6f22.tar.gz qemu-16d4e418e98feeb53f28d17eeffb198fe0fd6f22.tar.bz2 |
intel_iommu: Flush stage-1 cache in iotlb invalidation
According to spec, Page-Selective-within-Domain Invalidation (11b):
1. IOTLB entries caching second-stage mappings (PGTT=010b) or pass-through
(PGTT=100b) mappings associated with the specified domain-id and the
input-address range are invalidated.
2. IOTLB entries caching first-stage (PGTT=001b) or nested (PGTT=011b)
mapping associated with specified domain-id are invalidated.
So per spec definition the Page-Selective-within-Domain Invalidation
needs to flush first stage and nested cached IOTLB entries as well.
We don't support nested yet and pass-through mapping is never cached,
so what in iotlb cache are only first-stage and second-stage mappings.
Add a tag pgtt in VTDIOTLBEntry to mark PGTT type of the mapping and
invalidate entries based on PGTT type.
Signed-off-by: Zhenzhong Duan <zhenzhong.duan@intel.com>
Reviewed-by: Clément Mathieu--Drif<clement.mathieu--drif@eviden.com>
Acked-by: Jason Wang <jasowang@redhat.com>
Reviewed-by: Yi Liu <yi.l.liu@intel.com>
Message-Id: <20241212083757.605022-11-zhenzhong.duan@intel.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'rust')
0 files changed, 0 insertions, 0 deletions