2021-06-14 13:27:56

by Claudio Imbrenda

[permalink] [raw]
Subject: [PATCH v4 0/2] mm: add vmalloc_no_huge and use it

Add vmalloc_no_huge and export it, so modules can allocate memory with
small pages.

Use the newly added vmalloc_no_huge in KVM on s390 to get around a
hardware limitation.

v3->v4:
* reword commit messages to be more clear
* add comment in the second patch

v2->v3:
* do not export __vmalloc_node_range
* add vmalloc_no_huge as a wrapper around __vmalloc_node_range
* use vmalloc_no_huge instead of __vmalloc_node_range in kvm on s390x

Cc: Andrew Morton <[email protected]>
Cc: Nicholas Piggin <[email protected]>
Cc: Uladzislau Rezki (Sony) <[email protected]>
Cc: Catalin Marinas <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: Ingo Molnar <[email protected]>
Cc: David Rientjes <[email protected]>
Cc: Christoph Hellwig <[email protected]>

Claudio Imbrenda (2):
mm/vmalloc: add vmalloc_no_huge
KVM: s390: prepare for hugepage vmalloc

arch/s390/kvm/pv.c | 7 ++++++-
include/linux/vmalloc.h | 1 +
mm/vmalloc.c | 16 ++++++++++++++++
3 files changed, 23 insertions(+), 1 deletion(-)

--
2.31.1


2021-06-15 00:00:42

by Andrew Morton

[permalink] [raw]
Subject: Re: [PATCH v4 0/2] mm: add vmalloc_no_huge and use it

On Mon, 14 Jun 2021 15:23:55 +0200 Claudio Imbrenda <[email protected]> wrote:

> Add vmalloc_no_huge and export it, so modules can allocate memory with
> small pages.
>
> Use the newly added vmalloc_no_huge in KVM on s390 to get around a
> hardware limitation.

Thanks. I added

Fixes: 121e6f3258fe3 ("mm/vmalloc: hugepage vmalloc mappings")

and also addressed the whitespace thing which Christoph noted.

No cc:stable since 121e6f3258fe3 wasn't in 5.12.