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 15:20:52 +0100 [thread overview]
Message-ID: <aRSXxKacvz4h9_Th@alpha.franken.de> (raw)
In-Reply-To: <alpine.DEB.2.21.2511121046350.25436@angie.orcam.me.uk>
On Wed, Nov 12, 2025 at 12:16:28PM +0000, Maciej W. Rozycki wrote:
> On Wed, 12 Nov 2025, Thomas Bogendoerfer wrote:
>
> > > 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 :-(
>
> Oh dear! Something to do with the cache? Or code alignment perhaps?
code alignment is probably the trigger. It's reproducible on an R4400SC
and R5000 Indy, but not on a R4000SC Indy. Main difference other than
clock speed is L1 cache size...
And I've missremembered the R12k Octane problem. It's not a segmentation
fault but a bus error, because of an illegal instruction. I tracked it
down to a incorrect data in I-Cache (all 0 cache line, iirc), but never
found the reason for that.
> > Do you want to send a v2 of the patch ? I'm fine with the current version
> > for applying...
>
> I'll send v2 with an update for the Wired register as we talked. It may
> take a day or two.
no problem, thank you.
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 14:21 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
2025-11-12 12:16 ` Maciej W. Rozycki
2025-11-12 14:20 ` Thomas Bogendoerfer [this message]
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=aRSXxKacvz4h9_Th@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