From: Stefan Wiehler <stefan.wiehler@nokia.com>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Huacai Chen <chenhuacai@kernel.org>
Subject: Re: [PATCH v2] mips: mm: Call rcutree_report_cpu_starting() even earlier
Date: Wed, 1 Jul 2026 14:26:28 +0200 [thread overview]
Message-ID: <18fdaf3e-a957-4d9e-bc29-3c570d50f482@nokia.com> (raw)
In-Reply-To: <alpine.DEB.2.21.2605231440350.1450@angie.orcam.me.uk>
Hi Maciej,
> I'm afraid I have no QEMU installation ready to use, so I can't reproduce
> your steps without getting sidetracked. Would you be able to explain why
> it triggers with QEMU and possibly the I6400 CPU in particular, but not on
> real SMP hardware I have? From your commit description I infer this isn't
> supposed to be a heisenbug.
The only explanation that comes to my mind is that your platform has
TLBINV support and never calls r4k_tlb_uniquify() [1], therefore
skipping the kmalloc() call. Would you please verify that?
Kind regards,
Stefan
[1] https://git.kernel.org/pub/scm/linux/kernel/git/mips/linux.git/tree/arch/mips/mm/tlb-r4k.c?h=mips-fixes#n817
next prev parent reply other threads:[~2026-07-01 12:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 16:48 [PATCH v2] mips: mm: Call rcutree_report_cpu_starting() even earlier Stefan Wiehler
2026-04-10 13:04 ` Maciej W. Rozycki
2026-04-13 14:15 ` Stefan Wiehler
2026-04-22 12:16 ` Stefan Wiehler
2026-05-19 13:00 ` Stefan Wiehler
2026-05-23 13:49 ` Maciej W. Rozycki
2026-07-01 12:26 ` Stefan Wiehler [this message]
2026-07-02 10:38 ` Maciej W. Rozycki
2026-07-03 12:50 ` Stefan Wiehler
2026-04-11 8:52 ` Huacai Chen
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=18fdaf3e-a957-4d9e-bc29-3c570d50f482@nokia.com \
--to=stefan.wiehler@nokia.com \
--cc=chenhuacai@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=tsbogend@alpha.franken.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox