Re: [PATCH] iommu/vt-d: do not use flush-queue when caching-mode is on

On 1/27/21 8:26 AM, Lu Baolu wrote: +{ +    struct dmar_domain *dmar_domain = to_dmar_domain(domain); +    struct intel_iommu *iommu = domain_get_iommu(dmar_domain); + +    if (intel_iommu_strict) +    return 0; + +    /* + * The flush queue implementation does not perform page-selective

Re: [PATCH] iommu/vt-d: do not use flush-queue when caching-mode is on

Hi Nadav, On 1/27/21 4:38 AM, Nadav Amit wrote: From: Nadav Amit When an Intel IOMMU is virtualized, and a physical device is passed-through to the VM, changes of the virtual IOMMU need to be propagated to the physical IOMMU. The hypervisor therefore needs to monitor PTE mappings in the IOMMU

Re: [PATCH] iommu/vt-d: do not use flush-queue when caching-mode is on

> On Jan 26, 2021, at 4:26 PM, Lu Baolu wrote: > > Hi Nadav, > > On 1/27/21 4:38 AM, Nadav Amit wrote: >> From: Nadav Amit >> When an Intel IOMMU is virtualized, and a physical device is >> passed-through to the VM, changes of the virtual IOMMU need to be >> propagated to the physical IOMMU.

[PATCH] iommu/vt-d: do not use flush-queue when caching-mode is on

From: Nadav Amit When an Intel IOMMU is virtualized, and a physical device is passed-through to the VM, changes of the virtual IOMMU need to be propagated to the physical IOMMU. The hypervisor therefore needs to monitor PTE mappings in the IOMMU page-tables. Intel specifications provide