From: Michael Ellerman <mpe@ellerman•id.au>
To: pc@us•ibm.com, linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH v2] powerpc: A new cache geometry aux vectors
Date: Mon, 06 Mar 2017 16:46:46 +1100 [thread overview]
Message-ID: <87r32bot2x.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <288deec2-a821-316b-5e53-e186deda96f9@us.ibm.com>
Paul Clarke <pc@us•ibm.com> writes:
> P9 (with bad device-tree):
> --
> # ./cache_shape
> test: cache_shape
> tags: git_version:v4.10-0-gc470abd-dirty
> L1I cache size: 0 0B 0K
> L1I line size: 0x80 fully associative
> L1D cache size: 0 0B 0K
> L1D line size: 0x80 fully associative
> L2 cache size: 0 0B 0K
> L2 line size: 0 fully associative
> L3 cache size: 0 0B 0K
> L3 line size: 0 fully associative
> success: cache_shape
> --
Hmm, which p9 mambo is this? I get:
test: cache_shape
tags: git_version:v4.10-10927-g0a55d1671c33
L1I cache size: 0x8000 32768B 32K
L1I line size: 0x80 128-way associative
L1D cache size: 0x8000 32768B 32K
L1D line size: 0x80 128-way associative
L2 cache size: 0 0B 0K
L2 line size: 0 fully associative
L3 cache size: 0 0B 0K
L3 line size: 0 fully associative
success: cache_shape
So that looks OK, other than that here is no L2/L3 info.
I'm using mambo commit e0c03c93c6d14c5f842840cc4ac4183cb25e123b.
>
> Do you want me to Ack your v3 patch set in that thread?
No don't bother, it's already merged so your ack wouldn't get included
in the git history. This mail thread is record enough that it got
tested by someone other than me.
Thanks for testing.
cheers
next prev parent reply other threads:[~2017-03-06 5:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 6:22 [PATCH v2] powerpc: A new cache geometry aux vectors Benjamin Herrenschmidt
2017-03-01 20:53 ` Paul Clarke
2017-03-02 6:33 ` Michael Ellerman
2017-03-02 23:46 ` Paul Clarke
2017-03-03 4:01 ` Michael Ellerman
2017-03-03 13:51 ` Paul Clarke
2017-03-05 23:11 ` Benjamin Herrenschmidt
2017-03-06 5:46 ` Michael Ellerman [this message]
2017-03-06 8:24 ` Segher Boessenkool
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=87r32bot2x.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=pc@us$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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