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:	Thu, 03 Jan 2013 09:48:43 -0800
From:	"H. Peter Anvin" <>
To:	Konrad Rzeszutek Wilk <>
CC:	Fenghua Yu <>, Ingo Molnar <>,
	Thomas Gleixner <>,
	Asit K Mallick <>,
	Tigran Aivazian <>,
	Yinghai Lu <>,
	Andreas Herrmann <>,
	Borislav Petkov <>,
	linux-kernel <>, x86 <>
Subject: Re: [PATCH v5 00/12] x86/microcode: Early load microcode

On 01/03/2013 09:44 AM, Konrad Rzeszutek Wilk wrote:
> A couple of questions - why the usage of native_[read|write]_msr? I get the
> __native_cpuid variant, but I am not sure I understand why you are using
> the native_* variants. Especially as this code ends up being called on
> Xen and lguest (at least on 64-bit) and probably should go through the
> paravirt interfaces.

For Xen, the early microcode update should be done in the hypervisor launch.

However, if you have a more specific flow in mind please clarify.  Keep 
in mind Xen is largely a black box to non-Xen developers
(#include <stdrant.h>).


P.S. Since when is lguest 64-bit?  Did I miss something?

H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists