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]
Date:	Sun, 6 May 2012 02:46:29 +0300
From:	Ido Yariv <ido@...ery.com>
To:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>
Cc:	Shai Fultheim <shai@...lemp.com>, Ido Yariv <ido@...ery.com>
Subject: Re: [PATCH RESEND] x86: cache_info: Fix setup of l2/l3 ids

On Fri, Apr 20, 2012 at 1:09 AM, Ido Yariv <ido@...ery.com> wrote:
> From: Shai Fultheim <shai@...lemp.com>
>
> On some architectures (such as vSMP), it is possible to have CPUs with a
> different number of cores sharing the same cache.
>
> The current implementation implicitly assumes that all CPUs will have
> the same number of cores sharing caches, and as a result, different CPUs
> can end up with the same l2/l3 ids.
>
> Fix this by masking out the shared cache bits, instead of shifting the
> APICID. By doing so, it is guaranteed that the generated cache ids are
> always unique.
>
> Signed-off-by: Shai Fultheim <shai@...lemp.com>
> [ido@...ery.com: rebased, simplified, and reworded the commit message]
> Signed-off-by: Ido Yariv <ido@...ery.com>

Ping?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ