From: Borislav Petkov <bp@suse.de>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org, tglx@linutronix.de,
mingo@redhat.com, hpa@zytor.com
Subject: Re: [PATCH] x86/amd: Derive L3 shared_cpu_map from cpu_llc_shared_mask
Date: Wed, 26 Jul 2017 05:51:23 +0200 [thread overview]
Message-ID: <20170726035123.GA30702@nazgul.tnic> (raw)
In-Reply-To: <1500544328-2132-1-git-send-email-suravee.suthikulpanit@amd.com>
On Thu, Jul 20, 2017 at 04:52:08AM -0500, Suravee Suthikulpanit wrote:
> With X86_FEATURE_TOPOEXT, current logic default to using APIC ID
> to calculate cpumask for shared_cpu_map. However, since APIC IDs
> are not guarantee to be contiguous for cores across different L3,
> such as in family17h system w/ downcore configuration.
> This results in incorrect L3 shared_cpu_map.
There are syntactic and formulation errors in this paragraph, it reads
funny. Please improve.
> Instead, it should be safe to always use the pre-calculated
> cpu_llc_shared_mask to derive L3 shared_cpu_map.
"should"?!?
What does that mean? You tested it on relevant machines or you're hoping
that nothing would go wrong?
> Signed-off-by: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
> ---
> arch/x86/kernel/cpu/intel_cacheinfo.c | 28 ++++++++++++++--------------
> 1 file changed, 14 insertions(+), 14 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/intel_cacheinfo.c b/arch/x86/kernel/cpu/intel_cacheinfo.c
> index c55fb2c..10427bb 100644
> --- a/arch/x86/kernel/cpu/intel_cacheinfo.c
> +++ b/arch/x86/kernel/cpu/intel_cacheinfo.c
> @@ -811,7 +811,20 @@ static int __cache_amd_cpumap_setup(unsigned int cpu, int index,
> struct cacheinfo *this_leaf;
> int i, sibling;
>
> - if (boot_cpu_has(X86_FEATURE_TOPOEXT)) {
> + if (index == 3) {
> + for_each_cpu(i, cpu_llc_shared_mask(cpu)) {
> + this_cpu_ci = get_cpu_cacheinfo(i);
> + if (!this_cpu_ci->info_list)
> + continue;
> + this_leaf = this_cpu_ci->info_list + index;
> + for_each_cpu(sibling, cpu_llc_shared_mask(cpu)) {
> + if (!cpu_online(sibling))
> + continue;
> + cpumask_set_cpu(sibling,
> + &this_leaf->shared_cpu_map);
> + }
> + }
> + } else if (boot_cpu_has(X86_FEATURE_TOPOEXT)) {
So this leaves more questions open than before it:
* Is cpu_llc_shared_map now *the* mask for the L3?
* Is the X86_FEATURE_TOPOEXT thing still going to be used for the other cache
levels? Apparently yes, I guess.
IOW, what is the big picture here? I could use some more details in the
commit message about it.
--
Regards/Gruss,
Boris.
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)
--
prev parent reply other threads:[~2017-07-26 3:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 9:52 Suravee Suthikulpanit
2017-07-26 3:51 ` 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=20170726035123.GA30702@nazgul.tnic \
--to=bp@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=suravee.suthikulpanit@amd.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®