From: Andy Lutomirski <luto@MIT.EDU>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Cc: Fenghua Yu <fenghua.yu@intel.com>,
Matthew Garrett <mjg59@srcf.ucam.org>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andy Lutomirski <luto@MIT.EDU>
Subject: [PATCH v4 0/2] Forcibly enable some MISC_ENABLE features on Intel
Date: Wed, 17 Aug 2011 10:03:17 -0400 [thread overview]
Message-ID: <cover.1313586473.git.luto@mit.edu> (raw)
Intel allows BIOS or the OS to enable or disable some CPU fueatures via
IA32_MISC_ENABLE. I have machines that don't enable fast strings or
monitor/mwait in BIOS, so do it on bootup instead.
Changes from v3:
- Don't display CPU index (and therefore don't break !SMP build)
- Don't display "Failed to enable..." when kmemcheck is on
Changes from v2:
- Don't linebreak printk messages (for ease of grepping)
- Use printk_once
- Update the "Disabled fast string operations" message
Changes from v1:
- Display FW_WARN messages.
- Don't change the kmemcheck message.
- Improve the fast string comment.
- Improve the changelogs.
Andy Lutomirski (2):
x86: Enable fast strings on Intel if BIOS hasn't already
x86: Enable monitor/mwait on Intel if BIOS hasn't already
arch/x86/kernel/cpu/intel.c | 51 ++++++++++++++++++++++++++++++++++++++----
1 files changed, 46 insertions(+), 5 deletions(-)
--
1.7.6
next reply other threads:[~2011-08-17 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 14:03 Andy Lutomirski [this message]
2011-08-17 14:03 ` [PATCH v4 1/2] x86: Enable fast strings on Intel if BIOS hasn't already Andy Lutomirski
2011-08-17 21:38 ` Yu, Fenghua
2011-08-17 14:03 ` [PATCH v4 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=cover.1313586473.git.luto@mit.edu \
--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