linux-kernel - Re: [PATCH v5 00/12] x86/microcode: Early load microcode

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: <50EC77DB.6090300@zytor.com>
Date:	Tue, 08 Jan 2013 11:47:39 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Konrad Rzeszutek Wilk <konrad@...nel.org>
CC:	Fenghua Yu <fenghua.yu@...el.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Asit K Mallick <asit.k.mallick@...el.com>,
	Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
	Yinghai Lu <yinghai@...nel.org>,
	Andreas Herrmann <andreas.herrmann3@....com>,
	Borislav Petkov <borislav.petkov@....com>,
	linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH v5 00/12] x86/microcode: Early load microcode

On 01/08/2013 11:46 AM, Konrad Rzeszutek Wilk wrote:
> 
> OK. I am trying to figure out whether this usage of native_* for the
> MSRs was done on purpose - and it sounds like the answer is no. If so -
> can it be done using the normal 'safe_rdmsr' and 'wrmsr'?
> 
> That would allow at least in the case of Xen, to omit a whole bunch
> of MSR writes/reads during the boot that are not neccessary as we would
> not trap in the hypervisor - but could use the pvops version of
> read/write MSR calls to just do a nop.
> 

Why is this code invoked on Xen at all?  That seems crazy.

	-hpa


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