[lkml]   [2001]   [Sep]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: flush_tlb_all in vmalloc_area_pages
On Thu, Sep 20, 2001 at 02:26:38PM -0700, David S. Miller wrote:
> From: Andrea Arcangeli <>
> Date: Fri, 7 Sep 2001 16:56:12 +0200
> For the flush_cache_all for the virtually indexed caches should be the
> same issue in theory (at least the kmap logic only needs to flush the
> caches before the unmapping [not before the mapping] too)
> Am I missing something, Dave?
> Anything that creates or takes away vmalloc() mappings needs to flush
> the data cache if it is virtuall indexed.

The only question I'd like to get a answer is "what is actually the
data that can be virtually indexed) in the vmalloc range at the time we
run vmalloc?" Where does it cames from?

If there is no such data (as I think), we obviously don't need to flush
the virtually indexed caches at vmalloc time (but just at vfree).

Furthmore I recall on sparc you cannot flush the cache if you don't have
a mapping in place, and when you run vmalloc there should be no mapping
in place for the region of cache that you're trying to flush (or we
wouldn't trap the invalid faults there).

If anybody is using at boot time the vmalloc range for whatever purpuse
it should be its own business to flush the cache before dropping the
mappings from there.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:03    [W:0.064 / U:1.724 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site