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 v2 0/2] Forcibly enable some MISC_ENABLE features on Intel
Date: Sat, 6 Aug 2011 07:42:34 -0400 [thread overview]
Message-ID: <cover.1312630712.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.
The Intel SDM volume 3, appendix B.1 says that the OS should not touch
the monitor enable bit if SSE3 is not present, which presumably means
that the OS may touch that bit if SSE3 is present. In any case, these
patches seem to work.
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 | 50 ++++++++++++++++++++++++++++++++++++++++--
1 files changed, 47 insertions(+), 3 deletions(-)
--
1.7.6
next reply other threads:[~2011-08-06 11:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 11:42 Andy Lutomirski [this message]
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
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=cover.1312630712.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;
as well as URLs for NNTP newsgroup(s).