From: Konrad Rzeszutek Wilk <konrad@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Fenghua Yu <fenghua.yu@intel.com>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Asit K Mallick <asit.k.mallick@intel.com>,
Tigran Aivazian <tigran@aivazian.fsnet.co.uk>,
Yinghai Lu <yinghai@kernel.org>,
Andreas Herrmann <andreas.herrmann3@amd.com>,
Borislav Petkov <borislav.petkov@amd.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH v5 00/12] x86/microcode: Early load microcode
Date: Tue, 8 Jan 2013 14:46:34 -0500 [thread overview]
Message-ID: <20130108194633.GA15194@phenom.dumpdata.com> (raw)
In-Reply-To: <50E5C47B.6060707@zytor.com>
On Thu, Jan 03, 2013 at 09:48:43AM -0800, H. Peter Anvin wrote:
> 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.
Right. That is the plan.
>
> 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>).
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.
>
> -hpa
>
> P.S. Since when is lguest 64-bit? Did I miss something?
Oh, I assumed it could do it.
>
> --
> 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 majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2013-01-08 19:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 7:44 [PATCH v5 00/12] x86/microcode: Early load microcode Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 01/12] Documentation/x86: " Fenghua Yu
2013-01-31 22:25 ` [tip:x86/microcode] x86, doc: Documentation for early microcode loading tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 02/12] x86/microcode_intel.h: Define functions and macros for early loading ucode Fenghua Yu
2013-01-31 22:26 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 03/12] x86/common.c: Make have_cpuid_p() a global function Fenghua Yu
2013-01-31 22:27 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 04/12] x86/common.c: load ucode in 64 bit or show loading ucode info in 32 bit on AP Fenghua Yu
2013-01-31 22:28 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 05/12] x86/microcode_core_early.c: Define interfaces for early loading ucode Fenghua Yu
2013-01-31 22:29 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 06/12] x86/microcode_intel_lib.c: Early update ucode on Intel's CPU Fenghua Yu
2013-01-31 22:31 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 07/12] x86/tlbflush.h: Define __native_flush_tlb_global_irq_disabled() Fenghua Yu
2013-01-31 22:32 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 08/12] x86/microcode_intel_early.c: Early update ucode on Intel's CPU Fenghua Yu
2013-01-31 22:33 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 09/12] x86/head_32.S: Early update ucode in 32-bit Fenghua Yu
2013-01-31 22:34 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 10/12] x86/head64.c: Early update ucode in 64-bit Fenghua Yu
2013-01-31 22:35 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 11/12] x86/mm/init.c: Copy ucode from initrd image to kernel memory Fenghua Yu
2013-01-31 22:37 ` [tip:x86/microcode] " tip-bot for Fenghua Yu
2012-12-21 7:44 ` [PATCH v5 12/12] x86/Kconfig: Configurations to enable/disable the feature Fenghua Yu
2013-01-31 22:38 ` [tip:x86/microcode] x86/Kconfig: Make early microcode loading a configuration feature tip-bot for Fenghua Yu
2013-01-03 17:44 ` [PATCH v5 00/12] x86/microcode: Early load microcode Konrad Rzeszutek Wilk
2013-01-03 17:48 ` H. Peter Anvin
2013-01-08 19:46 ` Konrad Rzeszutek Wilk [this message]
2013-01-08 19:47 ` H. Peter Anvin
2013-01-08 20:04 ` Konrad Rzeszutek Wilk
2013-01-08 20:16 ` H. Peter Anvin
2013-01-09 13:35 ` Konrad Rzeszutek Wilk
2023-10-09 12:29 ` [tip: x86/microcode] x86/microcode/32: Move early loading after paging enable tip-bot2 for Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130108194633.GA15194@phenom.dumpdata.com \
--to=konrad@kernel.org \
--cc=andreas.herrmann3@amd.com \
--cc=asit.k.mallick@intel.com \
--cc=borislav.petkov@amd.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tigran@aivazian.fsnet.co.uk \
--cc=x86@kernel.org \
--cc=yinghai@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.