From: Heiko Carstens <hca@linux.ibm.com>
To: Luiz Capitulino <luizcap@redhat.com>
Cc: Gerald Schaefer <gerald.schaefer@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
borntraeger@linux.ibm.com, joao.m.martins@oracle.com,
mike.kravetz@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, linux-s390@vger.kernel.org,
gor@linux.ibm.com, agordeev@linux.ibm.com, osalvador@suse.de,
akpm@linux-foundation.org, aneesh.kumar@kernel.org
Subject: Re: [PATCH v2] s390: fix HugeTLB vmemmap optimization crash
Date: Thu, 30 Oct 2025 15:56:21 +0100 [thread overview]
Message-ID: <20251030145621.16837Bd6-hca@linux.ibm.com> (raw)
In-Reply-To: <bdd4ea3a-f326-4eb8-866a-52b1ea2bdc5a@redhat.com>
On Thu, Oct 30, 2025 at 10:54:47AM -0400, Luiz Capitulino wrote:
> On 2025-10-30 10:38, Gerald Schaefer wrote:
> > On Wed, 29 Oct 2025 13:49:53 +0100
> > Heiko Carstens <hca@linux.ibm.com> wrote:
> > Therefore, we should disable ARCH_WANT_OPTIMIZE_HUGETLB_VMEMMAP again, for
> > now. Doing it right would most likely require common code changes and
> > CRDTE / CSPG usage on s390. Not sure if this feature is really worth the
> > hassle, reading all the drawbacks that I mentioned in my commit 00a34d5a99c0
> > ("s390: select ARCH_WANT_HUGETLB_PAGE_OPTIMIZE_VMEMMAP").
>
> OK, let's do the right thing. Do you plan to post a patch? I can do it
> if you would like.
It is already in your inbox :)
prev parent reply other threads:[~2025-10-30 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 21:15 [PATCH v2] s390: fix HugeTLB vmemmap optimization crash Luiz Capitulino
2025-10-28 21:53 ` Andrew Morton
2025-10-30 14:59 ` Heiko Carstens
2025-10-29 6:36 ` Alexander Gordeev
2025-10-29 9:57 ` David Hildenbrand
2025-10-29 10:44 ` Heiko Carstens
2025-10-29 12:15 ` David Hildenbrand
2025-10-29 12:49 ` Heiko Carstens
2025-10-30 14:38 ` Gerald Schaefer
2025-10-30 14:54 ` Luiz Capitulino
2025-10-30 14:56 ` Heiko Carstens [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=20251030145621.16837Bd6-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=joao.m.martins@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=luizcap@redhat.com \
--cc=mike.kravetz@oracle.com \
--cc=osalvador@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.