[PATCH] freepgt: remove arch pgd_addr_end
ia64 and sparc64 hurriedly had to introduce their own variants of pgd_addr_end, to leapfrog over the holes in their virtual address spaces which the final clear_page_range suddenly presented when converted from pgd_index to pgd_addr_end. But now that free_pgtables respects the vma list, those holes are never presented, and the arch variants can go. 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:
committed by
Linus Torvalds
parent
3bf5ee9564
commit
8f6c99c11a
@@ -561,32 +561,6 @@ do { \
|
||||
#define __HAVE_ARCH_PGD_OFFSET_GATE
|
||||
#define __HAVE_ARCH_LAZY_MMU_PROT_UPDATE
|
||||
|
||||
/*
|
||||
* Override for pgd_addr_end() to deal with the virtual address space holes
|
||||
* in each region. In regions 0..4 virtual address bits are used like this:
|
||||
* +--------+------+--------+-----+-----+--------+
|
||||
* | pgdhi3 | rsvd | pgdlow | pmd | pte | offset |
|
||||
* +--------+------+--------+-----+-----+--------+
|
||||
* 'pgdlow' overflows to pgdhi3 (a.k.a. region bits) leaving rsvd==0
|
||||
*/
|
||||
#define IA64_PGD_OVERFLOW (PGDIR_SIZE << (PAGE_SHIFT-6))
|
||||
|
||||
#define pgd_addr_end(addr, end) \
|
||||
({ unsigned long __boundary = ((addr) + PGDIR_SIZE) & PGDIR_MASK; \
|
||||
if (REGION_NUMBER(__boundary) < 5 && \
|
||||
__boundary & IA64_PGD_OVERFLOW) \
|
||||
__boundary += (RGN_SIZE - 1) & ~(IA64_PGD_OVERFLOW - 1);\
|
||||
(__boundary - 1 < (end) - 1)? __boundary: (end); \
|
||||
})
|
||||
|
||||
#define pmd_addr_end(addr, end) \
|
||||
({ unsigned long __boundary = ((addr) + PMD_SIZE) & PMD_MASK; \
|
||||
if (REGION_NUMBER(__boundary) < 5 && \
|
||||
__boundary & IA64_PGD_OVERFLOW) \
|
||||
__boundary += (RGN_SIZE - 1) & ~(IA64_PGD_OVERFLOW - 1);\
|
||||
(__boundary - 1 < (end) - 1)? __boundary: (end); \
|
||||
})
|
||||
|
||||
#include <asm-generic/pgtable-nopud.h>
|
||||
#include <asm-generic/pgtable.h>
|
||||
|
||||
|
Reference in New Issue
Block a user