From: Peter Zijlstra <peterz@infradead.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: "Brown, Len" <len.brown@intel.com>, Len Brown <lenb@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: [PATCH 05/11] x86 topology: export die_siblings
Date: Wed, 20 Feb 2019 11:58:50 +0100 [thread overview]
Message-ID: <20190220105850.GC17969@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <70ea25e2-6538-77ec-8686-40567e8d362b@linux.intel.com>
On Tue, Feb 19, 2019 at 02:33:59PM -0500, Liang, Kan wrote:
> Besides the generic document, I think we should update x86 document as well,
> which is in Documentation/x86/topology.txt.
>
> The definition of topology_core_cpumask has to be changed to per die, right?
That's what the change to match_die() did. It limits the core mask.
next prev parent reply other threads:[~2019-02-20 10:58 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190219032259.12237-1-len.brown@intel.com>
2019-02-19 3:22 ` [PATCH 01/11] x86 topology: fix doc typo Len Brown
2019-02-19 3:40 ` Len Brown
2019-02-19 3:22 ` [PATCH 02/11] topolgy: simplify cputopology.txt formatting and wording Len Brown
2019-02-19 3:40 ` Len Brown
2019-02-19 19:33 ` Randy Dunlap
2019-02-19 20:33 ` [linux-drivers-review] " Brown, Len
2019-02-19 3:22 ` [PATCH 03/11] x86 topology: Add CPUID.1F multi-die/package support Len Brown
2019-02-19 3:40 ` Len Brown
2019-02-19 16:49 ` Liang, Kan
2019-02-19 19:27 ` Brown, Len
2019-02-20 2:59 ` Like Xu
2019-02-20 6:10 ` Len Brown
2019-02-20 10:55 ` Peter Zijlstra
2019-02-20 15:08 ` Len Brown
2019-02-26 13:54 ` Peter Zijlstra
2019-02-28 15:59 ` Len Brown
2019-02-28 17:56 ` Peter Zijlstra
2019-02-24 10:04 ` Brice Goglin
2019-02-25 5:31 ` Like Xu
2019-02-25 8:08 ` Brown, Len
2019-02-19 3:22 ` [PATCH 04/11] cpu topology: export die_id Len Brown
2019-02-19 3:40 ` Len Brown
2019-02-19 3:22 ` [PATCH 05/11] x86 topology: export die_siblings Len Brown
2019-02-19 3:40 ` Len Brown
2019-02-19 16:56 ` Liang, Kan
2019-02-19 18:43 ` Brown, Len
2019-02-19 19:33 ` Liang, Kan
2019-02-20 10:58 ` Peter Zijlstra [this message]
2019-02-20 21:52 ` Brice Goglin
2019-02-21 7:41 ` Len Brown
2019-02-21 8:38 ` Brice Goglin
2019-02-19 3:22 ` [PATCH 11/11] hwmon/coretemp: Support multi-die/package Len Brown
2019-02-19 3:40 ` Len Brown
2019-02-19 15:08 ` Guenter Roeck
2019-02-19 16:46 ` Guenter Roeck
2019-02-19 3:40 ` [PATCH 06/11] x86 topology: define topology_unique_die_id() Len Brown
2019-02-19 3:40 ` [PATCH 07/11] powercap/intel_rapl: simplify rapl_find_package() Len Brown
2019-02-19 9:11 ` Rafael J. Wysocki
2019-02-19 3:40 ` [PATCH 08/11] powercap/intel_rapl: Support multi-die/package Len Brown
2019-02-19 9:10 ` Rafael J. Wysocki
2019-02-20 11:02 ` Peter Zijlstra
2019-02-21 5:44 ` Len Brown
2019-02-26 4:41 ` Len Brown
2019-02-26 6:55 ` Zhang Rui
2019-02-19 3:40 ` [PATCH 09/11] powercap/intel_rapl: update rapl domain name and debug messages Len Brown
2019-02-19 9:10 ` Rafael J. Wysocki
2019-02-19 3:40 ` [PATCH 10/11] thermal/x86_pkg_temp_thermal: Support multi-die/package Len Brown
2019-02-19 3:40 [PATCH 0/11] multi-die/package support Len Brown
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=20190220105850.GC17969@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=kan.liang@linux.intel.com \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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.