On Mon, 15 Jul 2019, Andi Kleen wrote: > > Right, we don't know where the PAT invocation comes from and whether they > > are safe to omit flushing the cache. The module load code would be one > > obvious candidate. > > Module load just changes the writable/executable status, right? That shouldn't > need to flush in any case because it doesn't change the caching attributes.
Ah right. We don't flush when the caching attributes are not changed.
Thanks,
tglx
