From: Stian Halseth <stian@itx.no>
To: Jan Engelhardt <ej@inai.de>
Cc: davem@davemloft.net, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: [PATCH] sparc: populate sysfs cache topology information on sun4v
Date: Thu, 22 Oct 2026 18:55:54 +0200 [thread overview]
Message-ID: <190b3c8b11b860dcd1dfed739f9f7a5690b35e5e.camel@itx.no> (raw)
In-Reply-To: <oo23630s-96q9-69n0-9457-764233rs5496@vanv.qr>
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
Hi Jan,
On Thu, 2026-10-22 at 18:17 +0200, Jan Engelhardt wrote:
> I did not even expect this to do anything sensible on V240.
> That is just an accident - and multicore-per-package (MC)
> sun4u are expected to be still misreported. That needs again
> different logic.
Right, so maybe just return -ENOENT on sun4u and leave it as it is? The
lscpu fallback already gets the single-core ones right.
>
> > Maybe it's simpler to just walk the MD directly in
> > init_cache_level()
> > and populate_cache_leaves(), following the same arcs as
> > fill_in_one_cpu(), and add one leaf per cache node?
>
> After some pondering and in anticipation of MC sun4u, I think
> re-walking is sensible. I expect there to be a few savings
> (just 24 per strand) and a bunch of LOC removals.
Sounds good. I'm happy to test v2 on my T4-1, T7-1 and V240 when it's
ready.
/Stian
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2026-10-22 16:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 22:27 Jan Engelhardt
2026-10-19 0:16 ` Tony Rodriguez
2026-10-19 0:37 ` Tony Rodriguez
2026-10-19 2:32 ` Tony Rodriguez
[not found] ` <c7d7a96c-feb9-4676-8cc2-73529e8324ef@gmail.com>
2026-10-19 2:42 ` Tony Rodriguez
2026-10-19 9:49 ` Stian Halseth
2026-10-22 16:17 ` Jan Engelhardt
2026-10-22 16:55 ` Stian Halseth [this message]
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=190b3c8b11b860dcd1dfed739f9f7a5690b35e5e.camel@itx.no \
--to=stian@itx.no \
--cc=davem@davemloft.net \
--cc=ej@inai.de \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.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®