linux-kernel - Re: [PATCH v3 2/2] x86/AMD: Group cpu_llc_id assignment by topology feature and family

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20161107072906.GA26938@gmail.com>
Date:   Mon, 7 Nov 2016 08:29:06 +0100
From:   Ingo Molnar <mingo@...nel.org>
To:     Borislav Petkov <bp@...e.de>
Cc:     x86@...nel.org, Yazen Ghannam <Yazen.Ghannam@....com>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 2/2] x86/AMD: Group cpu_llc_id assignment by topology
 feature and family


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

> Ditto, clean it up and add tags:
> 
> ---
> From: Yazen Ghannam <Yazen.Ghannam@....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