Re: [PATCH v4 05/22] iommu: Introduce cache_invalidate API

2019-03-06 Thread Jacob Pan
On Tue, 5 Mar 2019 19:14:42 +0100 Auger Eric wrote: > Hi Kevin, Yi, > > On 3/5/19 4:28 PM, Jean-Philippe Brucker wrote: > > On 18/02/2019 13:54, Eric Auger wrote: > >> From: "Liu, Yi L" > >> > >> In any virtualization use case, when the first translation stage > >> is "owned" by the guest

Re: [PATCH v4 05/22] iommu: Introduce cache_invalidate API

2019-03-05 Thread Auger Eric
Hi Kevin, Yi, On 3/5/19 4:28 PM, Jean-Philippe Brucker wrote: > On 18/02/2019 13:54, Eric Auger wrote: >> From: "Liu, Yi L" >> >> In any virtualization use case, when the first translation stage >> is "owned" by the guest OS, the host IOMMU driver has no knowledge >> of caching structure updates

Re: [PATCH v4 05/22] iommu: Introduce cache_invalidate API

2019-03-05 Thread Jean-Philippe Brucker
On 18/02/2019 13:54, Eric Auger wrote: > From: "Liu, Yi L" > > In any virtualization use case, when the first translation stage > is "owned" by the guest OS, the host IOMMU driver has no knowledge > of caching structure updates unless the guest invalidation activities > are trapped by the

[PATCH v4 05/22] iommu: Introduce cache_invalidate API

2019-02-18 Thread Eric Auger
From: "Liu, Yi L" In any virtualization use case, when the first translation stage is "owned" by the guest OS, the host IOMMU driver has no knowledge of caching structure updates unless the guest invalidation activities are trapped by the virtualizer and passed down to the host. Since the