Re: [RFC PATCH] Update the cachetlb.txt file WRT flush_dcache_page and update_mmu_cache

[Matthew Wilcox <matthew@wil.cx>]

On Mon, May 10, 2010 at 11:16:47AM +0100, Catalin Marinas wrote:
> In most situations, just doing flushing in set_pte_at() would suffice
> and flush_dcache_page() can be ignored. There are two situations where I
> still see flush_dcache_page() useful:
> 
>      1. SMP systems where the cache maintenance operations aren't
>         automatically broadcast in hardware
>      2. The kernel modifies a page cache page that is already mapped in
>         user space
> 
> (1) can be worked around on some architectures (though not sure about
> all of them).
> 
> Is (2) a valid scenario?

The kernel always calls kmap() / kunmap() around accesses to page cache
pages (thanks to x86-32's ability to support 64GB).  There are three
ways I know of that architectures use this:

1) No-ops.  These architectures don't have cache problems.
2) Flush the kernel's mapping in kunmap().  This can have bad consequences
in SMP systems with threaded programs.
3) Select an address in kmap() that will alias to the user's address.

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."