From: Andrew Morton <akpm@linux-foundation.org>
To: Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
linux-s390@vger.kernel.org, frankja@linux.ibm.com,
borntraeger@de.ibm.com, cohuck@redhat.com, david@redhat.com,
linux-mm@kvack.org, Nicholas Piggin <npiggin@gmail.com>,
Uladzislau Rezki <urezki@gmail.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
David Rientjes <rientjes@google.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH v4 0/2] mm: add vmalloc_no_huge and use it
Date: Mon, 14 Jun 2021 16:59:11 -0700 [thread overview]
Message-ID: <20210614165911.1ee6c9459ac7f746906e3f0b@linux-foundation.org> (raw)
In-Reply-To: <20210614132357.10202-1-imbrenda@linux.ibm.com>
On Mon, 14 Jun 2021 15:23:55 +0200 Claudio Imbrenda <imbrenda@linux.ibm.com> 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.
prev parent reply other threads:[~2021-06-14 23:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 13:23 Claudio Imbrenda
2021-06-14 13:23 ` [PATCH v4 1/2] mm/vmalloc: add vmalloc_no_huge Claudio Imbrenda
2021-06-14 13:44 ` David Hildenbrand
2021-06-14 13:55 ` Uladzislau Rezki
2021-06-14 15:21 ` Christoph Hellwig
2021-06-18 19:47 ` David Rientjes
2021-06-14 13:23 ` [PATCH v4 2/2] KVM: s390: prepare for hugepage vmalloc Claudio Imbrenda
2021-06-14 13:44 ` David Hildenbrand
2021-06-14 23:59 ` Andrew Morton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210614165911.1ee6c9459ac7f746906e3f0b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=borntraeger@de.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=hch@infradead.org \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=npiggin@gmail.com \
--cc=rientjes@google.com \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox