From: Borislav Petkov <bp@suse.de>
To: "Yu, Fenghua" <fenghua.yu@intel.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"Anvin, H Peter" <h.peter.anvin@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH] cacheinfo: Introduce cache id
Date: Fri, 1 Jul 2016 20:35:36 +0200 [thread overview]
Message-ID: <20160701183536.GE4749@pd.tnic> (raw)
In-Reply-To: <3E5A0FA7E9CA944F9D5414FEC6C712205DFD172A@ORSMSX106.amr.corp.intel.com>
On Fri, Jul 01, 2016 at 06:01:06PM +0000, Yu, Fenghua wrote:
> Cache id is unique on the same level of cache across platform.
Btw, I forgot to ask in the reply to Tony: how are those cache IDs
exactly going to be used? An example please...
> Could you check cpu#/cache/index#/shared_cpu_map or shared_cpu_list.
Bah, my kvm is on an AMD guest - forget what it says :-)
> Cache id is unique on the same level across platform.
>
> #find /sys/device/system/cpu/. -name id|xargs cat
Btw, you could do
grep . /sys/devices/system/cpu/cpu*/cache/index*/id
and it'll give you the absolute filepaths too, so that the output is
parseable easier.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
next prev parent reply other threads:[~2016-07-01 18:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 1:56 [PATCH] cacheinfo: Introduce cache id Fenghua Yu
2016-06-30 1:56 ` Fenghua Yu
2016-07-01 10:21 ` Borislav Petkov
2016-07-01 16:50 ` Luck, Tony
2016-07-01 17:27 ` Borislav Petkov
2016-07-01 18:00 ` Luck, Tony
2016-07-01 18:29 ` Borislav Petkov
2016-07-01 18:32 ` Yu, Fenghua
2016-07-01 18:40 ` Borislav Petkov
2016-07-01 19:08 ` Yu, Fenghua
2016-07-04 17:29 ` Borislav Petkov
2016-07-01 18:01 ` Yu, Fenghua
2016-07-01 18:35 ` Borislav Petkov [this message]
2016-07-01 19:24 ` Yu, Fenghua
2016-07-04 17:58 ` Borislav Petkov
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=20160701183536.GE4749@pd.tnic \
--to=bp@suse.de \
--cc=eranian@google.com \
--cc=fenghua.yu@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.