[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1609082131540.5454@nanos>
Date: Thu, 8 Sep 2016 21:33:37 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Fenghua Yu <fenghua.yu@...el.com>
cc: "H. Peter Anvin" <h.peter.anvin@...el.com>,
Ingo Molnar <mingo@...e.hu>, Tony Luck <tony.luck@...el.com>,
Peter Zijlstra <peterz@...radead.org>,
Tejun Heo <tj@...nel.org>, Borislav Petkov <bp@...e.de>,
Stephane Eranian <eranian@...gle.com>,
Marcelo Tosatti <mtosatti@...hat.com>,
David Carrillo-Cisneros <davidcc@...gle.com>,
Shaohua Li <shli@...com>,
Ravi V Shankar <ravi.v.shankar@...el.com>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
Sai Prakhya <sai.praneeth.prakhya@...el.com>,
linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH v2 02/33] Documentation, ABI: Add a document entry for
cache id
On Thu, 8 Sep 2016, Fenghua Yu wrote:
> +What: /sys/devices/system/cpu/cpu*/cache/index*/id
> +Date: July 2016
> +Contact: Linux kernel mailing list <linux-kernel@...r.kernel.org>
> +Description: Cache id
> +
> + The id identifies a hardware cache of the system within a given
> + cache index in a set of cache indices. The "index" name is
> + simply a nomenclature from CPUID's leaf 4 which enumerates all
> + caches on the system by referring to each one as a cache index.
> + The (cache index, cache id) pair is unique for the whole
> + system.
> +
> + Currently id is implemented on x86. On other platforms, id is
> + not enabled yet.
And it never will be available on anything else than x86 because there is
no other architecture providing CPUID leaf 4 ....
If you want this to be generic then get rid of the x86isms in the
explanation and describe the x86 specific part seperately.
Thanks,
tglx
Powered by blists - more mailing lists