linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v3 2/2] x86/AMD: Group cpu_llc_id assignment by topology feature and family
Date: Mon, 7 Nov 2016 08:29:06 +0100	[thread overview]
Message-ID: <20161107072906.GA26938@gmail.com> (raw)
In-Reply-To: <20161102201541.zdr23pt4seyrlhyf@pd.tnic>


* Borislav Petkov <bp@suse.de> wrote:

> Ditto, clean it up and add tags:
> 
> ---
> From: Yazen Ghannam <Yazen.Ghannam@amd.com>
> Date: Tue, 1 Nov 2016 11:51:03 -0500
> Subject: [PATCH] x86/AMD: Group cpu_llc_id assignment
> 
> Currently, we assume that a system has multiple last level caches only
> if there are multiple nodes, and that the cpu_llc_id is equal to the
> node_id. This no longer applies since Fam17h can have multiple last
> level caches within a node.

Wondering what the practical effect of this is - is any current hardware affected, 
and if yes, what are the effects of this patch?

Thanks,

	Ingo

  reply	other threads:[~2016-11-07  7:29 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 [this message]
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
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=20161107072906.GA26938@gmail.com \
    --to=mingo@kernel.org \
    --cc=Yazen.Ghannam@amd.com \
    --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 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).