Dan Williams <dan.j.williams@xxxxxxxxx> writes: > > The underlying issue is that the x86-PAT implementation wants to > ensure that conflicting mappings are not set up for the same physical > address. This is mentioned in the developer manuals as problematic on > some cpus. Andi, is lookup_memtype() and track_pfn_insert() still > relevant? There have been discussions about it in the past, and the right answer will likely differ for different CPUs: But so far the official answer for Intel CPUs is that these caching conflicts should be avoided. So I guess the cache in the original email makes sense for now. -Andi
