Re: [PATCH 5/5] iommufd: Flush CPU caches on DMA pages in non-coherent domains
From: Jason Gunthorpe
Date: Wed May 15 2024 - 16:43:21 EST
On Wed, May 15, 2024 at 03:06:36PM +0800, Yan Zhao wrote:
> > So it has to be calculated on closer to a page by page basis (really a
> > span by span basis) if flushing of that span is needed based on where
> > the pages came from. Only pages that came from a hwpt that is
> > non-coherent can skip the flushing.
> Is area by area basis also good?
> Isn't an area either not mapped to any domain or mapped into all domains?
Yes, this is what the span iterator turns into in the background, it
goes area by area to cover things.
> But, yes, considering the limited number of non-coherent domains, it appears
> more robust and clean to always flush for non-coherent domain in
> iopt_area_fill_domain().
> It eliminates the need to decide whether to retain the area flag during a split.
And flush for pin user pages, so you basically always flush because
you can't tell where the pages came from.
Jason