From: Tony Rodriguez <unixpro1970@gmail.com>
To: Jan Engelhardt <jengelh@inai.de>
Cc: davem@davemloft.net, sparclinux@vger.kernel.org,
linux-kernel@vger.kernel.org,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Stian Halseth <stian@itx.no>
Subject: Re: [PATCH] sparc: populate sysfs cache topology information on sun4v
Date: Mon, 26 Oct 2026 12:18:26 -0700 [thread overview]
Message-ID: <dcf2c329-9268-488a-8b7a-79419e49293c@gmail.com> (raw)
In-Reply-To: <CANmkgULrJwKSuwQhZjgL0-zWgMYWgOZLhseDXGtp_XwjcAayow@mail.gmail.com>
On 10/26/26 11:52 AM, Tony Rodriguez wrote:
> Tested-by: Tony Rodriguez <unixpro1970@gmail.com>
>
> Tested on both SPARC T7-1 and S7-2 systems; the lscpu output is correct on both.
>
> A) T7-1:
> A1) lscpu
> Architecture: sparc64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Big Endian
> CPU(s): 256
> On-line CPU(s) list: 0-255
> Model name: SPARC-M7
> Thread(s) per core: 8
> Core(s) per socket: 32
> Socket(s): 1
> Flags: sun4v
> Caches (sum of all):
> L1d: 512 KiB (32 instances)
> L1i: 512 KiB (32 instances)
> L2d: 4 MiB (16 instances)
> L2i: 2 MiB (8 instances)
> L3: 64 MiB (8 instances)
> NUMA:
> NUMA node(s): 1
> NUMA node0 CPU(s): 0-255
>
> A2) lscpu --cache
> NAME ONE-SIZE ALL-SIZE WAYS TYPE LEVEL SETS PHY-LINE COHERENCY-SIZE
> L1d 16K 512K 4 Data 1 128 32
> L1i 16K 512K 4 Instruction 1 64 64
> L2d 256K 4M 8 Data 2 512 64
> L2i 256K 2M 8 Instruction 2 512 64
> L3 8M 64M 8 Unified 3 16384 64
>
> B) S7-2:
> B1) lscpu
> Architecture: sparc64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Big Endian
> CPU(s): 128
> On-line CPU(s) list: 0-127
> Model name: SPARC-S7 (Sonoma)
> Thread(s) per core: 8
> Core(s) per socket: 8
> Socket(s): 2
> Flags: sun4v
> Caches (sum of all):
> L1d: 256 KiB (16 instances)
> L1i: 256 KiB (16 instances)
> L2d: 2 MiB (8 instances)
> L2i: 1 MiB (4 instances)
> L3: 32 MiB (4 instances)
> NUMA:
> NUMA node(s): 2
> NUMA node0 CPU(s): 0-63
> NUMA node1 CPU(s): 64-127
>
> B2) lscpu --cache
> NAME ONE-SIZE ALL-SIZE WAYS TYPE LEVEL SETS PHY-LINE COHERENCY-SIZE
> L1d 16K 256K 4 Data 1 128 32
> L1i 16K 256K 4 Instruction 1 64 64
> L2d 256K 2M 8 Data 2 512 64
> L2i 256K 1M 8 Instruction 2 512 64
> L3 8M 32M 8 Unified 3 16384 64
Corrected the lscpu --cache output to fix the PHY-LINE and
COHERENCY-SIZE fields, making the output easier to read in the email.
next prev parent reply other threads:[~2026-10-26 19:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <X-TH#1.20261018222723.43442-1-jengelh@inai.de>
2026-10-26 18:52 ` Tony Rodriguez
2026-10-26 19:18 ` Tony Rodriguez [this message]
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
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=dcf2c329-9268-488a-8b7a-79419e49293c@gmail.com \
--to=unixpro1970@gmail.com \
--cc=davem@davemloft.net \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jengelh@inai.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
--cc=stian@itx.no \
/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®