mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anthony Yznaga <anthony.yznaga@oracle.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	sparclinux@vger.kernel.org, davem@davemloft.net,
	andreas@gaisler.com
Cc: linux-kernel@vger.kernel.org, agordeev@linux.ibm.com,
	will@kernel.org, ryan.roberts@arm.com, david@redhat.com,
	osalvador@suse.de
Subject: Re: [PATCH] sparc64: fix hugetlb for sun4u
Date: Wed, 16 Jul 2025 09:47:11 -0700	[thread overview]
Message-ID: <04cf759e-9d99-4826-997b-06ede4e7dbd9@oracle.com> (raw)
In-Reply-To: <1821f2fc2e339fbb4bc6a4af1748a3462f501392.camel@physik.fu-berlin.de>



On 7/16/25 1:41 AM, John Paul Adrian Glaubitz wrote:
> Hi Anthony,
> 
> On Wed, 2025-07-16 at 08:18 +0200, John Paul Adrian Glaubitz wrote:
>> On Tue, 2025-07-15 at 18:24 -0700, Anthony Yznaga wrote:
>>> An attempt to exercise sparc hugetlb code in a sun4u-based guest
>>> running under qemu results in the guest hanging due to being stuck
>>> in a trap loop. This is due to invalid hugetlb TTEs being installed
>>> that do not have the expected _PAGE_PMD_HUGE and page size bits set.
>>> Although the breakage has gone apparently unnoticed for several years,
>>> fix it now so there is the option to exercise sparc hugetlb code under
>>> qemu. This can be useful because sun4v support in qemu does not support
>>> linux guests currently and sun4v-based hardware resources may not be
>>> readily available.
>>
>> It has actually been observed for a long time that newer kernels are
>> unstable on sun4u while there are no stability issues on sun4v.
> 
> Just as a heads-up: I'm currently building a Debian kernel with this patch
> and see if this fixes the stability issues we're seeing on UltraSPARC machines.

If it's the use of hugetlb that is causing problems then this patch 
should help.

> 
>> I'm not sure though whether the Debian kernel enables hugetlb by default.
> 
> We do.
> 
> I'll report back.
> 
> Adrian
> 


  reply	other threads:[~2025-07-16 16:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  1:24 Anthony Yznaga
2025-07-16  6:18 ` John Paul Adrian Glaubitz
2025-07-16  8:41   ` John Paul Adrian Glaubitz
2025-07-16 16:47     ` Anthony Yznaga [this message]
2025-07-24 10:52     ` John Paul Adrian Glaubitz
2025-07-25  5:59 ` John Paul Adrian Glaubitz
2025-07-25 20:46 ` John Paul Adrian Glaubitz
2025-07-25 21:09   ` John Paul Adrian Glaubitz
2025-08-08 21:31 ` John Paul Adrian Glaubitz
2025-08-08 22:15   ` Anthony Yznaga
2025-08-08 22:37     ` John Paul Adrian Glaubitz
2025-08-09  6:23       ` John Paul Adrian Glaubitz
2025-08-09  6:26         ` John Paul Adrian Glaubitz
2025-08-09  6:42           ` John Paul Adrian Glaubitz
2025-08-10  9:52             ` John Paul Adrian Glaubitz
2025-08-10 22:20               ` John Paul Adrian Glaubitz
2025-08-11  8:25                 ` David Hildenbrand
2025-08-11 10:44                 ` John Paul Adrian Glaubitz
2025-08-11 11:06                   ` John Paul Adrian Glaubitz
2025-08-12 12:32                   ` Found it - was: " John Paul Adrian Glaubitz
2025-08-12 12:34                     ` John Paul Adrian Glaubitz
2025-08-21 12:52                     ` David Hildenbrand
2025-08-21 15:03                       ` Edgecombe, Rick P
2025-08-21 16:42                         ` John Paul Adrian Glaubitz
2025-08-11  8:20         ` David Hildenbrand
2025-08-11  8:28           ` John Paul Adrian Glaubitz
2025-09-19 18:01 ` Andreas Larsson

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=04cf759e-9d99-4826-997b-06ede4e7dbd9@oracle.com \
    --to=anthony.yznaga@oracle.com \
    --cc=agordeev@linux.ibm.com \
    --cc=andreas@gaisler.com \
    --cc=davem@davemloft.net \
    --cc=david@redhat.com \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osalvador@suse.de \
    --cc=ryan.roberts@arm.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=will@kernel.org \
    /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

all inboxes | Powered by JetHome®