Hugh Dickins 4d6ddfa924 [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>		2005-10-29 21:40:37 -07:00
..
fault.c	[SPARC64]: Kill all external references to sp_banks[]	2005-09-28 21:46:43 -07:00
generic.c	[SPARC]: Kill io_remap_page_range()	2005-09-01 21:51:26 -07:00
hugetlbpage.c	[PATCH] Hugepage consolidation	2005-06-21 18:46:15 -07:00
init.c	[SPARC64]: Fix boot failures on SunBlade-150	2005-10-12 12:22:46 -07:00
Makefile	[SPARC64]: Convert to use generic exception table support.	2005-09-28 20:21:11 -07:00
tlb.c	[PATCH] mm: tlb_is_full_mm was obscure	2005-10-29 21:40:37 -07:00
ultra.S	[SPARC64]: Fix powering off on SMP.	2005-10-14 15:26:08 -07:00