From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Nick Bowler <nbowler@draconx.ca>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: mm: Prevent a TLB shutdown on initial uniquification
Date: Wed, 12 Nov 2025 10:56:05 +0100 [thread overview]
Message-ID: <aRRZtbBdCfEEhad9@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2511111340330.25436@angie.orcam.me.uk>
On Tue, Nov 11, 2025 at 03:41:50PM +0000, Maciej W. Rozycki wrote:
> On Tue, 11 Nov 2025, Thomas Bogendoerfer wrote:
>
> > > Can you please give it a try with your systems?
> >
> > it's booting on my R4400 SGI Indy, but I see a lot of segmentation
> > faults during system start. If I comment out r4k_tlb_uniquify() every-
> > thing boots fine, which is kind of strange as there is a local_flush_tlb_all(),
> > which should leave the TLB in the same stage.... No idea why, yet.
>
> Can you try the diagnostic patch below, which is what I used to verify
> this change, and report the entries produced? Otherwise I wonder whether
> I haven't missed a barrier somewhere.
Update on the issue: Your patch is good and the segmentation faults,
I'm seeing, have IMHO a different reason. Instead of removing the call
to r4k_tlb_uniquify() I've replaced the jal in the binary with a nop.
And the issue is still there with this patched kernel. I've seen
something similair on a R12k Octanes, which comes and goes probably
depeding on code layout. So far I wasn't able to nail this down :-(
Do you want to send a v2 of the patch ? I'm fine with the current version
for applying...
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2025-11-12 9:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 6:21 [PATCH] MIPS: mm: Prevent a TLB shutdown on initial uniquification Maciej W. Rozycki
2025-11-11 12:27 ` Thomas Bogendoerfer
2025-11-11 15:41 ` Maciej W. Rozycki
2025-11-11 22:53 ` Thomas Bogendoerfer
2025-11-12 9:56 ` Thomas Bogendoerfer [this message]
2025-11-12 12:16 ` Maciej W. Rozycki
2025-11-12 14:20 ` Thomas Bogendoerfer
2025-11-12 23:47 ` Maciej W. Rozycki
2025-11-11 22:17 ` Nick Bowler
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=aRRZtbBdCfEEhad9@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=nbowler@draconx.ca \
/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