From: Borislav Petkov <bp@alien8.de>
To: Jamie Gloudon <jamie.gloudon@gmail.com>
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 15:46:02 +0200 [thread overview]
Message-ID: <20121002134602.GA5015@x1.osrc.amd.com> (raw)
In-Reply-To: <20121002131138.GA1387@darkstar>
On Tue, Oct 02, 2012 at 09:11:38AM -0400, Jamie Gloudon wrote:
> 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
Yes, there's a perf callback from within the ucode driver to recheck
PEBS. This is in 3.6 so PEBS should work there with the required ucode
patch.
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-10-02 13:45 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
2012-10-02 13:46 ` Borislav Petkov [this message]
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=20121002134602.GA5015@x1.osrc.amd.com \
--to=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=jamie.gloudon@gmail.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 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.