[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <dcc3a478c4f31059686dca38691c4d135d16dc7d.camel@physik.fu-berlin.de>
Date: Thu, 21 Aug 2025 18:42:35 +0200
From: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
To: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>, "andreas@...sler.com"
<andreas@...sler.com>, "anthony.yznaga@...cle.com"
<anthony.yznaga@...cle.com>, "davem@...emloft.net" <davem@...emloft.net>,
"david@...hat.com" <david@...hat.com>, "sparclinux@...r.kernel.org"
<sparclinux@...r.kernel.org>
Cc: "agordeev@...ux.ibm.com" <agordeev@...ux.ibm.com>, "osalvador@...e.de"
<osalvador@...e.de>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "will@...nel.org" <will@...nel.org>,
"mroos@...ux.ee"
<mroos@...ux.ee>, "ryan.roberts@....com" <ryan.roberts@....com>
Subject: Re: Found it - was: Re: [PATCH] sparc64: fix hugetlb for sun4u
Hi,
On Thu, 2025-08-21 at 15:03 +0000, Edgecombe, Rick P wrote:
> And actually one of the architectures that was broken was sparc, which got fixed in
> d3c976c14ad8 ("sparc64: Fix regression in non-hypervisor TLB flush xcall"). John
> was going to explore whether the fix might have been incomplete.
Investigations regarding the origin of the problem are still ongoing. The issue is
definitely related to SPARC-specific mm code, more specifically the TLB management
code on Cheetah-based UltraSPARC systems.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Powered by blists - more mailing lists