| From: |
| Nicholas Piggin <npiggin-AT-gmail.com> |
| To: |
| linux-mm-AT-kvack.org |
| Subject: |
| [PATCH v3 0/8] huge vmalloc mappings |
| Date: |
| Mon, 10 Aug 2020 12:27:24 +1000 |
| Message-ID: |
| <20200810022732.1150009-1-npiggin@gmail.com> |
| Cc: |
| Nicholas Piggin <npiggin-AT-gmail.com>, linux-kernel-AT-vger.kernel.org, linux-arch-AT-vger.kernel.org, linuxppc-dev-AT-lists.ozlabs.org, Catalin Marinas <catalin.marinas-AT-arm.com>, Will Deacon <will-AT-kernel.org>, linux-arm-kernel-AT-lists.infradead.org, Thomas Gleixner <tglx-AT-linutronix.de>, Ingo Molnar <mingo-AT-redhat.com>, Borislav Petkov <bp-AT-alien8.de>, x86-AT-kernel.org, "H. Peter Anvin" <hpa-AT-zytor.com>, Zefan Li <lizefan-AT-huawei.com> |
| Archive-link: |
| Article |
Not tested on x86 or arm64, would appreciate a quick test there so I can
ask Andrew to put it in -mm. Other option is I can disable huge vmallocs
for them for the time being.
Since v2:
- Rebased on vmalloc cleanups, split series into simpler pieces.
- Fixed several compile errors and warnings
- Keep the page array and accounting in small page units because
struct vm_struct is an interface (this should fix x86 vmap stack debug
assert). [Thanks Zefan]
Nicholas Piggin (8):
mm/vmalloc: fix vmalloc_to_page for huge vmap mappings
mm: apply_to_pte_range warn and fail if a large pte is encountered
mm/vmalloc: rename vmap_*_range vmap_pages_*_range
lib/ioremap: rename ioremap_*_range to vmap_*_range
mm: HUGE_VMAP arch support cleanup
mm: Move vmap_range from lib/ioremap.c to mm/vmalloc.c
mm/vmalloc: add vmap_range_noflush variant
mm/vmalloc: Hugepage vmalloc mappings
.../admin-guide/kernel-parameters.txt | 2 +
arch/arm64/mm/mmu.c | 10 +-
arch/powerpc/mm/book3s64/radix_pgtable.c | 8 +-
arch/x86/mm/ioremap.c | 10 +-
include/linux/io.h | 9 -
include/linux/vmalloc.h | 13 +
init/main.c | 1 -
mm/ioremap.c | 231 +--------
mm/memory.c | 60 ++-
mm/vmalloc.c | 442 +++++++++++++++---
10 files changed, 453 insertions(+), 333 deletions(-)
--
2.23.0
