From: Borislav Petkov <bp@suse.de>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Luck, Tony" <tony.luck@intel.com>,
"Yu, Fenghua" <fenghua.yu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Anvin, H Peter" <h.peter.anvin@intel.com>,
Ingo Molnar <mingo@elte.hu>,
Stephane Eranian <eranian@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Vikas Shivappa <vikas.shivappa@linux.intel.com>,
"Shankar, Ravi V" <ravi.v.shankar@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH v2 2/3] Documentation, ABI: Add a document entry for cache id
Date: Sat, 9 Jul 2016 10:17:16 +0200 [thread overview]
Message-ID: <20160709081716.GA8725@pd.tnic> (raw)
In-Reply-To: <20160708193457.GA18734@gmail.com>
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)
--
next prev parent reply other threads:[~2016-07-09 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 22:07 [PATCH v2 0/3] Cache id Fenghua Yu
2016-07-06 22:07 ` [PATCH v2 1/3] cacheinfo: Introduce cache id Fenghua Yu
2016-07-06 22:07 ` [PATCH v2 2/3] Documentation, ABI: Add a document entry for " Fenghua Yu
2016-07-08 8:41 ` Ingo Molnar
2016-07-08 17:06 ` Yu, Fenghua
2016-07-08 17:29 ` Luck, Tony
2016-07-08 18:07 ` Ingo Molnar
2016-07-08 18:41 ` Borislav Petkov
2016-07-08 18:47 ` Luck, Tony
2016-07-08 18:55 ` Borislav Petkov
2016-07-08 19:34 ` Ingo Molnar
2016-07-09 8:17 ` Borislav Petkov [this message]
2016-07-08 18:06 ` Ingo Molnar
2016-07-06 22:07 ` [PATCH v2 3/3] x86, intel_cacheinfo: Enable cache id in x86 Fenghua Yu
2016-07-07 16:21 ` [PATCH v2 0/3] Cache id Borislav Petkov
2016-07-08 3:13 ` Yu, Fenghua
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=20160709081716.GA8725@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=mingo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).