From: "H. Peter Anvin" <hpa@zytor.com>
To: "Bryan O'Donoghue" <bryan.odonoghue.lkml@nexus-software.ie>
Cc: Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org, x86@kernel.org,
fenghua.yu@intel.com
Subject: Re: [PATCH] x86: Add check for P5 to microcode_intel_early
Date: Sat, 20 Apr 2013 08:52:55 -0700 [thread overview]
Message-ID: <2cca7cab-e8b2-41fc-b757-22f37b78f99b@email.android.com> (raw)
In-Reply-To: <51725ED4.8020001@nexus-software.ie>
I committed my own patch yesterday; at this point it would be most helpful if you could test it out to make sure it works as it should...
Bryan O'Donoghue <bryan.odonoghue.lkml@nexus-software.ie> wrote:
>On 20/04/13 00:13, H. Peter Anvin wrote:
>> On 04/19/2013 02:44 PM, Bryan O'Donoghue wrote:
>>> On 19/04/13 22:25, Borislav Petkov wrote:
>>>> On Fri, Apr 19, 2013 at 10:55:15PM +0200, Borislav Petkov wrote:
>>>>> Just filter out P5 and earlier. The code already does that for
>CPUs
>>>>> which don't have CPUID.
>>>>
>>>> Actually, an alternative - more practical albeit not very accurate
>>>
>>> More practical ? Hmm - the MSRs don't exist for< P5
>>>
>>>> solution would be to check for which families Intel delivers
>microcode
>>>> and do the cut off there with a comment as to why you do it like
>>>> that.void
>>>
>>> You mean return !intel so this function will never be called.
>>>
>>> __init load_ucode_bsp(void)
>>> {
>>> int vendor = x86_vendor();
>>>
>>> if (vendor == X86_VENDOR_INTEL)
>>> load_ucode_intel_bsp();
>>> }
>>>
>>> Ah yes. That would work and be less code.
>>>
>>> We should do it that way.
>>
>> Do you think you can have a patch for me in the next few hours?
>
>Sure.
>
>I'm in Ireland (sleeping @ 00:15 on a Friday night sadly).
>
>Give me ~ 40 minutes
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2013-04-20 15:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 17:23 Bryan O'Donoghue
2013-04-19 19:11 ` Borislav Petkov
2013-04-19 20:35 ` Bryan O'Donoghue
2013-04-19 20:55 ` Borislav Petkov
2013-04-19 21:25 ` Borislav Petkov
2013-04-19 21:44 ` Bryan O'Donoghue
2013-04-19 22:02 ` H. Peter Anvin
2013-04-19 23:13 ` H. Peter Anvin
2013-04-20 9:24 ` Bryan O'Donoghue
2013-04-20 15:52 ` H. Peter Anvin [this message]
2013-04-20 0:20 ` [tip:x86/urgent] x86, microcode: Verify the family before dispatching microcode patching tip-bot for H. Peter Anvin
2013-04-20 16:21 ` Bryan O'Donoghue
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=2cca7cab-e8b2-41fc-b757-22f37b78f99b@email.android.com \
--to=hpa@zytor.com \
--cc=bp@alien8.de \
--cc=bryan.odonoghue.lkml@nexus-software.ie \
--cc=fenghua.yu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome