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
| ||
|
Date: Tue, 21 Feb 2012 12:20:42 +0100 From: Borislav Petkov <bp@...64.org> To: Daniel J Blueman <daniel@...ascale-asia.com> Cc: Andreas Herrmann <andreas.herrmann3@....com>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, "H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org, Steffen Persvold <sp@...ascale.com>, Borislav Petkov <borislav.petkov@....com> Subject: Re: [PATCH] x86: Remove wrong error message in x86_default_fixup_cpu_id On Tue, Feb 21, 2012 at 11:05:21AM +0000, Daniel J Blueman wrote: > The check and fixup wasn't needed in the Intel path thus far, so > wasn't added. > > We could specialise the 'if (c->phys_proc_id != node)' test to check > for x86_cpuinit.fixup_cpu_id being NULL and drop the default > override, if that is preferred? Before that, why do you need that check in the AMD path at all? Please give a more detailed explanation as to why is it needed on the AMD path at all. Thanks. -- Regards/Gruss, Boris. Advanced Micro Devices GmbH Einsteinring 24, 85609 Dornach GM: Alberto Bozzo Reg: Dornach, Landkreis Muenchen HRB Nr. 43632 WEEE Registernr: 129 19551 -- 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