linux-kernel - Re: [PATCH -v2 0/2] x86, microcode: Reload ucode only per-system

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: <20120630174503.GA24854@aftab.osrc.amd.com>
Date:	Sat, 30 Jun 2012 19:45:03 +0200
From:	Borislav Petkov <bp@...64.org>
To:	"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...nel.org>
Cc:	X86-ML <x86@...nel.org>, Thomas Gleixner <tglx@...utronix.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	Borislav Petkov <borislav.petkov@....com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH -v2 0/2] x86, microcode: Reload ucode only per-system

Assuming there are no more objections to those, can we get them into,
say, tip:x86/microcode for a wider, linux-next testing?

Peter's stuff could go there too or through the perf tree - it's kinda
arbitrary though.

Thanks.

On Thu, Jun 21, 2012 at 02:07:15PM +0200, Borislav Petkov wrote:
> From: Borislav Petkov <borislav.petkov@....com>
> 
> Ok, here's the second version with all review comments addressed. I've
> dropped the stable tag since this has been that way (and b0rked) since
> forever so stable rules don't apply.
> 
> We can probably do single backports if distros want it.
> 
> 
> 
> Changelog:
> 
> -v1:
> 
> Once upon a time there was this microcode reloading interface
> /sys/devices/system/cpu/cpuX/microcode/reload, where X is an online
> cpu on the system, which allowed the loading of microcode in a per-cpu
> manner.
> 
> This had problems like having different ucode revisions on an otherwise
> homogeneous system and needed O(n^2) overhead when tracking minimum
> microcode revision per-core.
> 
> So make this interface per-system so that it does microcode reloading on
> the whole system only.
> 
> Single commit messages have more info too.
> 
> The first patch has a stable tag which I'd like to see in stable but
> since it is not fixing a direct regression, I'd like to not push it
> upstream now but have it get tested in linux-next and go upstream during
> the next merge window from where it can trickle slowly to stable.
> 
> Patches have been tested on all AMD families, it wouldn't hurt if it saw
> some Intel testing too, although it should just work.
> 
> Holler if you see regressions/problems with it.
> 
> 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/