mirror of
https://github.com/Fishwaldo/Star64_linux.git
synced 2025-06-28 01:21:58 +00:00
[PATCH] mm: tlb_is_full_mm was obscure
tlb_is_full_mm? What does that mean? The TLB is full? No, it means that the mm's last user has gone and the whole mm is being torn down. And it's an inline function because sparc64 uses a different (slightly better) "tlb_frozen" name for the flag others call "fullmm". And now the ptep_get_and_clear_full macro used in zap_pte_range refers directly to tlb->fullmm, which would be wrong for sparc64. Rather than correct that, I'd prefer to scrap tlb_is_full_mm altogether, and change sparc64 to just use the same poor name as everyone else - is that okay? Signed-off-by: Hugh Dickins <hugh@veritas.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
This commit is contained in:
parent
15a23ffa2f
commit
4d6ddfa924
7 changed files with 8 additions and 37 deletions
|
@ -178,12 +178,6 @@ tlb_finish_mmu (struct mmu_gather *tlb, unsigned long start, unsigned long end)
|
|||
put_cpu_var(mmu_gathers);
|
||||
}
|
||||
|
||||
static inline unsigned int
|
||||
tlb_is_full_mm(struct mmu_gather *tlb)
|
||||
{
|
||||
return tlb->fullmm;
|
||||
}
|
||||
|
||||
/*
|
||||
* Logically, this routine frees PAGE. On MP machines, the actual freeing of the page
|
||||
* must be delayed until after the TLB has been flushed (see comments at the beginning of
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue