From: Michael Tokarev <mjt@tls.msk.ru>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: H Peter Anvin <hpa@zytor.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 v4 00/11] x86/microcode: Early load microcode
Date: Fri, 21 Dec 2012 13:04:38 +0400 [thread overview]
Message-ID: <50D42626.40708@msgid.tls.msk.ru> (raw)
In-Reply-To: <1356032893-2730-1-git-send-email-fenghua.yu@intel.com>
On 20.12.2012 23:48, Fenghua Yu wrote:
> From: Fenghua Yu <fenghua.yu@intel.com>
>
> The problem in current microcode loading method is that we load a microcode way,
> way too late; ideally we should load it before turning paging on. This may only
> be practical on 32 bits since we can't get to 64-bit mode without paging on,
> but we should still do it as early as at all possible.
Why loading microcode this early is important?
Why it is bad to load it at the end of (initial) boot?
Thanks,
/mjt
next prev parent reply other threads:[~2012-12-21 9:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 19:48 [PATCH v4 00/11] x86/microcode: Early load microcode Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 01/11] Documentation/x86: " Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 02/11] x86/microcode_intel.h: Define functions and macros for early loading ucode Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 03/11] x86/common.c: Make have_cpuid_p() a global function and load ucode or show ucode loading info on AP Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 04/11] x86/microcode_core_early.c: Define interfaces for early loading ucode Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 05/11] x86/microcode_intel_lib.c: Early update ucode on Intel's CPU Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 06/11] x86/tlbflush.h: Define __native_flush_tlb_global_irq_disabled() Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 07/11] x86/microcode_intel_early.c: Early update ucode on Intel's CPU Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 08/11] x86/head_32.S: Early update ucode in 32-bit Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 09/11] x86/head64.c: Early update ucode in 64-bit Fenghua Yu
2012-12-21 4:09 ` Yinghai Lu
2012-12-21 4:44 ` Yu, Fenghua
2012-12-21 5:07 ` Yu, Fenghua
[not found] ` <CAE9FiQVHuNkT3BLUW3hJf6mWbNq+kWmohwSNJMxxO1sYvyCxOQ@mail.gmail.com>
2012-12-21 5:48 ` H. Peter Anvin
2012-12-20 19:48 ` [PATCH v4 10/11] x86/mm/init.c: Copy ucode from initrd image to kernel memory Fenghua Yu
2012-12-20 19:48 ` [PATCH v4 11/11] x86/Kconfig: Configurations to enable/disable the feature Fenghua Yu
2012-12-21 9:04 ` Michael Tokarev [this message]
2012-12-21 15:09 ` [PATCH v4 00/11] x86/microcode: Early load microcode Yu, Fenghua
2012-12-21 15:14 ` Borislav Petkov
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=50D42626.40708@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--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.