From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: x86@kernel.org, Yazen Ghannam <Yazen.Ghannam@amd.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH v3 1/2] x86/AMD: Fix cpu_llc_id for AMD Fam17h systems
Date: Mon, 7 Nov 2016 08:31:21 +0100 [thread overview]
Message-ID: <20161107073121.GB26938@gmail.com> (raw)
In-Reply-To: <20161102201321.slgzk2x2ya4jzfax@pd.tnic>
* Borislav Petkov <bp@suse.de> wrote:
> Lemme clean up the commit message a bit more and add tags:
>
> ---
> From: Yazen Ghannam <Yazen.Ghannam@amd.com>
> Date: Tue, 1 Nov 2016 11:51:02 -0500
> Subject: [PATCH] x86/AMD: Fix cpu_llc_id for AMD Fam17h systems
>
> cpu_llc_id (Last Level Cache ID) derivation on AMD Fam17h has an
> underflow bug when extracting the socket_id value. It starts from 0
> so subtracting 1 from it will result in an invalid value. This breaks
> scheduling topology later on since the cpu_llc_id will be incorrect.
>
> The APIC ID is preset in APICx020 for bits 3 and above: they contain the
> core complex, node and socket IDs.
>
> The LLC is at the core complex level so we can find a unique cpu_llc_id
> by right shifting the APICID by 3 because then the least significant bit
> will be the Core Complex ID.
Same question as for the previous patch: what are the effects of the bug:
- Outright bad scheduling?
- Suboptimal scheduling?
- Crash?
- Something else?
Such information needs to be in commit messages, _especially_ when a Cc: stable
tag is added as well.
Thanks,
Ingo
next prev parent reply other threads:[~2016-11-07 7:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 16:51 [PATCH v3 1/2] x86/AMD: Fix cpu_llc_id for AMD Fam17h systems Yazen Ghannam
2016-11-01 16:51 ` [PATCH v3 2/2] x86/AMD: Group cpu_llc_id assignment by topology feature and family Yazen Ghannam
2016-11-02 20:15 ` Borislav Petkov
2016-11-07 7:29 ` Ingo Molnar
2016-11-07 9:22 ` Borislav Petkov
2016-11-02 20:13 ` [PATCH v3 1/2] x86/AMD: Fix cpu_llc_id for AMD Fam17h systems Borislav Petkov
2016-11-07 7:31 ` Ingo Molnar [this message]
2016-11-07 9:20 ` Borislav Petkov
2016-11-07 14:07 ` Ingo Molnar
2016-11-07 15:56 ` Borislav Petkov
2016-11-08 6:31 ` Ingo Molnar
2016-11-08 8:35 ` Borislav Petkov
2016-11-08 10:29 ` Ingo Molnar
2016-11-08 11:01 ` Borislav Petkov
2016-11-08 14:54 ` Ingo Molnar
2016-11-08 15:30 ` Borislav Petkov
2016-11-10 8:00 ` [tip:x86/cpu] x86/cpu/AMD: Clean up cpu_llc_id assignment per topology feature tip-bot for Yazen Ghannam
2016-11-09 16:13 ` [tip:x86/urgent] x86/cpu/AMD: Fix cpu_llc_id for AMD Fam17h systems tip-bot for Yazen Ghannam
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=20161107073121.GB26938@gmail.com \
--to=mingo@kernel.org \
--cc=Yazen.Ghannam@amd.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bp@suse.de \
--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.