linux-kernel - Re: [PATCH 1/2] x86, microcode: Correct microcode revision format

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:	Tue, 18 Oct 2011 08:13:16 -0700
From:	Andi Kleen <ak@...ux.intel.com>
To:	Borislav Petkov <bp@...64.org>
Cc:	Ingo Molnar <mingo@...e.hu>, X86-ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Borislav Petkov <borislav.petkov@....com>
Subject: Re: [PATCH 1/2] x86, microcode: Correct microcode revision format

On Mon, Oct 17, 2011 at 05:25:14PM +0200, Borislav Petkov wrote:
> From: Borislav Petkov <borislav.petkov@....com>
> 
> 506ed6b53e00ba303ad778122f08e1fca7cf5efb added microcode revision format
> to /proc/cpuinfo and the MCE handler in decimal format but both AMD and
> Intel patch levels are handled as hex numbers. Fix it.

Acked-by: Andi Kleen <ak@...ux.intel.com>

BTW if you want microcode output on AMD you'll need to implement
code to fill the field in on those CPUs.

-Andi
--
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/