From: tip-bot for Borislav Petkov <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: bp@suse.de, linux-kernel@vger.kernel.org, yazen.ghannam@amd.com,
peterz@infradead.org, hpa@zytor.com, bp@alien8.de,
tglx@linutronix.de, mingo@kernel.org
Subject: [tip:x86/urgent] x86/topology: Document cpu_llc_id
Date: Tue, 20 Dec 2016 01:34:37 -0800 [thread overview]
Message-ID: <tip-a268b5f1d6e4639fa6d78fc8bdddaebaa032ab24@git.kernel.org> (raw)
In-Reply-To: <20161117094557.jm6hwzdd52h7iwnj@pd.tnic>
Commit-ID: a268b5f1d6e4639fa6d78fc8bdddaebaa032ab24
Gitweb: http://git.kernel.org/tip/a268b5f1d6e4639fa6d78fc8bdddaebaa032ab24
Author: Borislav Petkov <bp@alien8.de>
AuthorDate: Thu, 17 Nov 2016 10:45:57 +0100
Committer: Ingo Molnar <mingo@kernel.org>
CommitDate: Tue, 20 Dec 2016 09:36:29 +0100
x86/topology: Document cpu_llc_id
It means different things on Intel and AMD so write it down so that
there's no confusion.
Signed-off-by: Borislav Petkov <bp@suse.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Yazen Ghannam <yazen.ghannam@amd.com>
Link: http://lkml.kernel.org/r/20161117094557.jm6hwzdd52h7iwnj@pd.tnic
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
Documentation/x86/topology.txt | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/x86/topology.txt b/Documentation/x86/topology.txt
index 06afac2..f3e9d7e 100644
--- a/Documentation/x86/topology.txt
+++ b/Documentation/x86/topology.txt
@@ -63,6 +63,15 @@ The topology of a system is described in the units of:
The maximum possible number of packages in the system. Helpful for per
package facilities to preallocate per package information.
+ - cpu_llc_id:
+
+ A per-CPU variable containing:
+ - On Intel, the first APIC ID of the list of CPUs sharing the Last Level
+ Cache
+
+ - On AMD, the Node ID or Core Complex ID containing the Last Level
+ Cache. In general, it is a number identifying an LLC uniquely on the
+ system.
* Cores:
prev parent reply other threads:[~2016-12-20 9:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 9:22 [PATCH] x86/topology: Document cpu_llc_id Borislav Petkov
2016-09-07 10:36 ` Peter Zijlstra
2016-11-14 6:29 ` Borislav Petkov
2016-11-17 9:45 ` [PATCH -v1.1] " Borislav Petkov
2016-11-17 12:57 ` Yazen Ghannam
2016-11-17 14:16 ` Borislav Petkov
2016-12-19 11:34 ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2016-12-20 9:34 ` tip-bot for Borislav Petkov [this message]
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=tip-a268b5f1d6e4639fa6d78fc8bdddaebaa032ab24@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yazen.ghannam@amd.com \
/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).