From: Andrew Lutomirski <luto@mit.edu>
To: "Yu, Fenghua" <fenghua.yu@intel.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Len Brown <lenb@kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v2 1/2] x86: Enable fast strings on Intel if BIOS hasn't already
Date: Sat, 6 Aug 2011 19:31:39 -0400 [thread overview]
Message-ID: <CAObL_7F2+eXTPo7a631Lh7GD_UpDQXgW_GSDp9Km7pwhwmM6Cw@mail.gmail.com> (raw)
In-Reply-To: <493994B35A117E4F832F97C4719C4C040132C5FB69@orsmsx505.amr.corp.intel.com>
On Sat, Aug 6, 2011 at 3:33 PM, Yu, Fenghua <fenghua.yu@intel.com> wrote:
>> -----Original Message-----
>> From: Andy Lutomirski [mailto:luto@MIT.EDU]
>> Sent: Saturday, August 06, 2011 4:43 AM
>> To: x86@kernel.org; linux-kernel@vger.kernel.org
>> Cc: Yu, Fenghua; Matthew Garrett; Len Brown; linux-
>> acpi@vger.kernel.org; Ingo Molnar; Andy Lutomirski
>> Subject: [PATCH v2 1/2] x86: Enable fast strings on Intel if BIOS
>> hasn't already
>>
>> Intel SDM volume 3A, 8.4.2 says:
>>
>> Software can disable fast-string operation by clearing the
>> fast-string-enable bit (bit 0) of IA32_MISC_ENABLE MSR.
>> However, Intel recomments that system software always enable
>> fast-string operation.
>>
>> The Intel DQ67SW board (with latest BIOS) disables fast string
>> operations if TXT is enabled. A Lenovo X220 disables it regardless
>> of TXT setting. I doubt I'm the only person with a dumb BIOS like
>> this.
>>
>> Signed-off-by: Andy Lutomirski <luto@mit.edu>
>> ---
>> arch/x86/kernel/cpu/intel.c | 25 ++++++++++++++++++++++---
>> 1 files changed, 22 insertions(+), 3 deletions(-)
>>
>> diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
>> index ed6086e..c80ab41 100644
>> --- a/arch/x86/kernel/cpu/intel.c
>> +++ b/arch/x86/kernel/cpu/intel.c
>> @@ -30,6 +30,7 @@
>> static void __cpuinit early_init_intel(struct cpuinfo_x86 *c)
>> {
>> u64 misc_enable;
>> + bool allow_fast_string = true;
>>
>> /* Unmask CPUID levels if masked: */
>> if (c->x86 > 6 || (c->x86 == 6 && c->x86_model >= 0xd)) {
>> @@ -118,8 +119,9 @@ static void __cpuinit early_init_intel(struct
>> cpuinfo_x86 *c)
>> * (model 2) with the same problem.
>> */
>> if (c->x86 == 15) {
>> - rdmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
>> + allow_fast_string = false;
>>
>> + rdmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
>> if (misc_enable & MSR_IA32_MISC_ENABLE_FAST_STRING) {
>> printk(KERN_INFO "kmemcheck: Disabling fast string
>> operations\n");
>>
>> @@ -130,11 +132,28 @@ static void __cpuinit early_init_intel(struct
>> cpuinfo_x86 *c)
>> #endif
>>
>> /*
>> - * If fast string is not enabled in IA32_MISC_ENABLE for any
>> reason,
>> - * clear the fast string and enhanced fast string CPU
>> capabilities.
>> + * If BIOS didn't enable fast string operation, try to enable
>> + * it ourselves. If that fails, then clear the fast string
>> + * and enhanced fast string CPU capabilities.
>> */
>> if (c->x86 > 6 || (c->x86 == 6 && c->x86_model >= 0xd)) {
>> rdmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
>> +
>> + if (allow_fast_string &&
>> + !(misc_enable & MSR_IA32_MISC_ENABLE_FAST_STRING)) {
>> + misc_enable |= MSR_IA32_MISC_ENABLE_FAST_STRING;
>> + wrmsr_safe(MSR_IA32_MISC_ENABLE, (u32)misc_enable,
>> + (u32)(misc_enable >> 32));
>> +
>> + /* Re-read to make sure it stuck. */
>> + rdmsrl(MSR_IA32_MISC_ENABLE, misc_enable);
>> +
>> + if (misc_enable & MSR_IA32_MISC_ENABLE_FAST_STRING)
>> + printk(KERN_WARNING FW_WARN "CPU #%d: "
>> + "IA32_MISC_ENABLE.FAST_STRING_ENABLE "
>> + "was not set", c->cpu_index);
> This printk is redundant because the same info is dumped in the below printk. Plus it's not firmware's issue if we can not set fast string bit 0 in MISC_ENABLE register. So I don't think FW_WARN is right.
Huh? This is the success path -- the patch prints the warning if
flipping the bit worked...
>
> I would suggest to remove this printk (and the if () statement) and change KERN_INFO to KERN_WARNING in the following printk.
>
>> + }
>> +
>> if (!(misc_enable & MSR_IA32_MISC_ENABLE_FAST_STRING)) {
>> printk(KERN_INFO "Disabled fast string
>> operations\n");
>> setup_clear_cpu_cap(X86_FEATURE_REP_GOOD);
...and this (which could be more clear) is displayed if flipping the
bit did not work, in which case the problem isn't BIOS's fault.
--Andy
next prev parent reply other threads:[~2011-08-06 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 11:42 [PATCH v2 0/2] Forcibly enable some MISC_ENABLE features on Intel Andy Lutomirski
2011-08-06 11:42 ` [PATCH v2 1/2] x86: Enable fast strings on Intel if BIOS hasn't already Andy Lutomirski
2011-08-06 19:33 ` Yu, Fenghua
2011-08-06 23:31 ` Andrew Lutomirski [this message]
2011-08-07 23:44 ` Yu, Fenghua
2011-08-09 15:00 ` Ingo Molnar
2011-08-09 15:12 ` Andrew Lutomirski
2011-08-08 18:42 ` Yu, Fenghua
2011-08-06 11:42 ` [PATCH v2 2/2] x86: Enable monitor/mwait " Andy Lutomirski
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=CAObL_7F2+eXTPo7a631Lh7GD_UpDQXgW_GSDp9Km7pwhwmM6Cw@mail.gmail.com \
--to=luto@mit.edu \
--cc=fenghua.yu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.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;
as well as URLs for NNTP newsgroup(s).