On Tue, 2006-08-08 at 10:48 -0400, Kyle McMartin wrote:
> On second thought, you've compressed two different flushes into
> flush_cache_vmap[1] where flush_tlb_all used to be...
> 
> I don't think this would be a problem because we're creating a
> new mapping, but James will probably prove my assumption wrong
> as usual. :)
> 
> [1 - flush_cache_vmap is just a flush_cache_all on the arches
>  I've looked at with VI-caches.]

The problem the flush_tlb_all() is trying to solve is to avoid stale tlb
entries in the ioremap area.  We're just being conservative by flushing
on both map and unmap.  Technically what vmalloc/vfree does (only flush
the tlb on unmap) is just fine because it means that the only tlb
entries in the remap area must belong to in-use mappings.

James


-
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to