All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: X86 ML <x86@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH] x86/topology: Document cpu_llc_id
Date: Wed,  7 Sep 2016 11:22:19 +0200	[thread overview]
Message-ID: <20160907092219.5523-1-bp@alien8.de> (raw)

From: Borislav Petkov <bp@suse.de>

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: Thomas Gleixner <tglx@linutronix.de>
---
 Documentation/x86/topology.txt | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/Documentation/x86/topology.txt b/Documentation/x86/topology.txt
index 06afac252f5b..7a5485730476 100644
--- a/Documentation/x86/topology.txt
+++ b/Documentation/x86/topology.txt
@@ -63,6 +63,12 @@ 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 containing the Last Level Cache.
 
 * Cores:
 
-- 
2.10.0

             reply	other threads:[~2016-09-07  9:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-07  9:22 Borislav Petkov [this message]
2016-09-07 10:36 ` [PATCH] x86/topology: Document cpu_llc_id 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

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=20160907092219.5523-1-bp@alien8.de \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --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.