[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20160709081716.GA8725@pd.tnic>
Date: Sat, 9 Jul 2016 10:17:16 +0200
From: Borislav Petkov <bp@...e.de>
To: Ingo Molnar <mingo@...nel.org>
Cc: "Luck, Tony" <tony.luck@...el.com>,
"Yu, Fenghua" <fenghua.yu@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Anvin, H Peter" <h.peter.anvin@...el.com>,
Ingo Molnar <mingo@...e.hu>,
Stephane Eranian <eranian@...gle.com>,
Peter Zijlstra <peterz@...radead.org>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@...el.com>,
linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH v2 2/3] Documentation, ABI: Add a document entry for
cache id
On Fri, Jul 08, 2016 at 09:34:57PM +0200, Ingo Molnar wrote:
> The cache-id identifies a hardware cache of the system within a given
> cache-index category of caches. The (cache-index,cache-id) pair is
I'd say something like:
"... 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. ... "
Because this way we hint at from where the "index" thing comes and
people can go and read the SDM for more info.
And also we're explaining what it is because, IMHO, whatever formulation
or spelling we do with "cache index", there's simply not a good way of
explaining what it means without *actually* explaining it and where it
comes from.
:-)
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
Powered by blists - more mailing lists