From: Jamie Gloudon <jamie.gloudon@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org, fenghua.yu@intel.com
Subject: Re: [PATCH 00/11] x86/microcode: Early load microcode
Date: Tue, 2 Oct 2012 09:11:38 -0400 [thread overview]
Message-ID: <20121002131138.GA1387@darkstar> (raw)
In-Reply-To: <20121002043954.GA27331@liondog.tnic>
On Tue, Oct 02, 2012 at 06:39:54AM +0200, Borislav Petkov wrote:
> On Mon, Oct 01, 2012 at 07:37:04PM -0400, Jamie Gloudon wrote:
> > On Mon, Oct 01, 2012 at 06:27:45PM +0200, Borislav Petkov wrote:
> > > On Mon, Oct 01, 2012 at 12:11:51PM -0400, Jamie Gloudon wrote:
> > > > Hey,
> > > >
> > > > Any chance of this getting merge for the 3.7 cycle?
> > >
> > > It is not ready yet: http://marc.info/?l=linux-kernel&m=134910582107898
> > >
> > > Out of curiosity: why do you nee it?
> > >
> > Seems like a better alternative to microcode_ctl which some distros don't
> > contain.
>
> [ Let me reorganize the mail chain as it should be,
> without top-posting. Please try not to top-post:
> http://curl.haxx.se/mail/etiquette.html#Do_Not_Top_Post ]
>
>
> Well,
>
> if you want to reload your microcode, you shouldn't be needing
> microcode_ctl (I believe this should be the case too on Intel, from
> staring at the code - on AMD it works).
>
> Basically, you simply put the microcode binaries into
> /lib/firmware/{amd,intel}-ucode/ and then do as root:
>
> $ echo 1 > /sys/devices/system/cpu/microcode/reload
>
> That's it, no need for special tools.
>
> --
> Regards/Gruss,
> Boris.
My main interest was getting PEBS events support for perf on Intel SNB cpus. Loading the microcode at runtime was not going to work.
However, thanks for pointing me in the right direction. I notice today this is not the case anymore from the thread below.
http://marc.info/?l=linux-kernel&m=133905353211963&w=2
Regards,
Jamie Gloudon
next prev parent reply other threads:[~2012-10-02 13:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 16:11 [PATCH 00/11] x86/microcode: Early load microcode Jamie Gloudon
2012-10-01 16:27 ` Borislav Petkov
2012-10-01 23:37 ` Jamie Gloudon
2012-10-02 4:39 ` Borislav Petkov
2012-10-02 13:11 ` Jamie Gloudon [this message]
2012-10-02 13:46 ` Borislav Petkov
2012-10-02 6:06 ` H. Peter Anvin
2012-10-02 19:00 ` Konrad Rzeszutek Wilk
2012-10-02 19:04 ` H. Peter Anvin
2012-10-03 13:13 ` Konrad Rzeszutek Wilk
2012-12-12 17:41 ` H. Peter Anvin
2012-10-02 19:04 ` Yu, Fenghua
-- strict thread matches above, loose matches on Subject: below --
2012-08-18 8:15 Fenghua Yu
2012-08-20 15:39 ` Borislav Petkov
2012-08-20 15:44 ` Yu, Fenghua
2012-08-20 18:51 ` H. Peter Anvin
2012-08-20 20:04 ` 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=20121002131138.GA1387@darkstar \
--to=jamie.gloudon@gmail.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).