From: Borislav Petkov <bp@amd64.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, andi@firstfloor.org
Subject: Re: [PATCH] perf/x86: fix microcode revision check for SNB-PEBS
Date: Fri, 24 Aug 2012 18:26:46 +0200 [thread overview]
Message-ID: <20120824162646.GE2297@aftab.osrc.amd.com> (raw)
In-Reply-To: <CABPqkBRV=2k34yfnr_y0fpftWab6YN2Q=qDKqA5xAW-R-r1bHg@mail.gmail.com>
On Fri, Aug 24, 2012 at 06:14:51PM +0200, Stephane Eranian wrote:
> So you're saying there is a cmdline tool that can use another
> interface to pass the ucode to the kernel. I am using the
> microcode_ctl on Ubuntu 11.04. Apparently that one is still using the
> old interface. But I may not be the only one in this situation then,
> so I think it's worth fixing now.
>
> What's the tool to update the ucode using the "new" interface then?
Well,
last time we talked about it:
http://marc.info/?l=linux-kernel&m=134012203712243 I was advocating the
following way:
Put ucode image into /lib/firmware/amd-ucode or /lib/firmware/intel-ucode and then do
$ echo 1 > /sys/devices/system/cpu/microcode/reload
which I think is the easiest but hpa had some reservations about it and
wanted to keep the old method too.
But looking at the code, this *actually* should work on Intel now too.
So, I'd say you can use both on Intel, it depends on them whatever they
decide to do in the future.
On AMD we have only the "echo 1" thing.
Alternatively, "rmmod microcode; modprobe microcode" works too but some
people wouldn't want to reload modules in order to update ucode.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2012-08-24 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 13:34 [PATCH] perf/x86: fix microcode revision check for SNB-PEBS Stephane Eranian
2012-08-24 16:08 ` Borislav Petkov
2012-08-24 16:14 ` Stephane Eranian
2012-08-24 16:26 ` Borislav Petkov [this message]
2012-08-27 17:18 ` [tip:perf/urgent] perf/x86: Fix " tip-bot for Stephane Eranian
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=20120824162646.GE2297@aftab.osrc.amd.com \
--to=bp@amd64.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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