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:	Sat, 22 Jan 2011 11:14:03 +0100
From:	Borislav Petkov <bp@...64.org>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, Tejun Heo <tj@...nel.org>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@....com>,
	"Richter, Robert" <robert.richter@....com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	"Rosenfeld, Hans" <Hans.Rosenfeld@....com>,
	Alok N Kataria <akataria@...are.com>,
	Stephen Hemminger <shemminger@...tta.com>,
	"Hans J. Koch" <hjk@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Move llc_shared_map out of cpu_info

On Fri, Jan 21, 2011 at 06:29:44PM -0500, Yinghai Lu wrote:
> 
> cpu_info is already with per_cpu, We can take llc_shared_map out of cpu_info,
> and declare it as per_cpu variable directly.
> 
> So later referencing could be simple and directly instead of diving to find
> cpu_info at first.
> 
> Also could make smp_store_cpu_info() much simple to avoid to do save and restore trick.
> 
> 
> Signed-off-by: Yinghai Lu <yinghai@...nel.org>

Yep, it's only natural to do that.

Acked-by: Borislav Petkov <borislav.petkov@....com>

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
General Managers: Alberto Bozzo, Andrew Bowd
Registration: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
--
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