From: Dave Jones <davej@redhat.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: Takashi Iwai <tiwai@suse.de>, "H. Peter Anvin" <hpa@zytor.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
x86@kernel.org, fenghua.yu@intel.com
Subject: Re: microcode loading got really slow.
Date: Thu, 23 May 2013 11:55:32 -0400 [thread overview]
Message-ID: <20130523155532.GE16419@redhat.com> (raw)
In-Reply-To: <CACVXFVP=9AJKGDM8hcrCv7+dQBtsqi39AFwFO2bsUxcrsGg2wQ@mail.gmail.com>
On Thu, May 23, 2013 at 11:27:08PM +0800, Ming Lei wrote:
> > Yes, in your case, everything is fine in the kernel itself. And no
> > microcode update is needed for new CPU, thus no firmware.
>
> Can the driver decide if the CPU need microcode? Or there will
> be the microcode for the CPU in future?
The kernel can't know. The microcode updates are asynchonously released
from the kernel. I might be running a months old kernel, and get a new
microcode tomorrow. The kernel handles this by looking for a file
with a name matching the cpu family/model/stepping. (See how they are
formed in /lib/firmware/intel-ucode/*)
DAve
next prev parent reply other threads:[~2013-05-23 15:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 23:03 microcode loading got really slow Dave Jones
2013-05-22 19:03 ` H. Peter Anvin
2013-05-22 20:00 ` Dave Jones
2013-05-22 20:09 ` H. Peter Anvin
2013-05-23 0:19 ` Dave Jones
2013-05-23 3:39 ` Dave Jones
2013-05-23 6:56 ` Takashi Iwai
2013-05-23 7:45 ` Ming Lei
2013-05-23 8:06 ` Takashi Iwai
2013-05-23 10:16 ` Takashi Iwai
2013-05-23 10:18 ` anish singh
2013-05-23 10:28 ` Takashi Iwai
2013-05-23 10:27 ` Ming Lei
2013-05-23 10:36 ` Takashi Iwai
2013-05-23 10:45 ` Ming Lei
2013-05-23 12:05 ` Takashi Iwai
2013-05-23 13:04 ` Ming Lei
2013-05-23 13:21 ` Takashi Iwai
2013-05-23 14:28 ` Ming Lei
2013-05-23 14:36 ` Takashi Iwai
2013-05-23 14:48 ` Dave Jones
2013-05-23 15:06 ` Takashi Iwai
2013-05-23 15:27 ` Ming Lei
2013-05-23 15:55 ` Dave Jones [this message]
2013-05-23 15:21 ` Ming Lei
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=20130523155532.GE16419@redhat.com \
--to=davej@redhat.com \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
--cc=tom.leiming@gmail.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox