From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: gang.wei@intel.com, JBeulich@suse.com,
xen-devel@lists.xenproject.org, andrew.cooper3@citrix.com,
ian.campbell@citrix.com, keir@xen.org, tim@xen.org
Subject: [RFC PATCH] THERM_CONTROL_MSR mucks with Xen cpufreq code.
Date: Fri, 18 Dec 2015 15:46:45 -0500 [thread overview]
Message-ID: <1450471606-19129-1-git-send-email-konrad.wilk@oracle.com> (raw)
Hey,
I've gotten feedback from some of the internal BIOS folks who had
noticied some issues (the machine is running very slowly) which we found
out was due to the ACPI DSDT being busted and the Linux kernel (dom0)
programming the _wrong_ values in the T-state MSR.
While this got fixed in the BIOS - it occurred to me that we really
shouldn't let dom0 poke at this MSR?
The patch that added this functionality didn't have much details.
next reply other threads:[~2015-12-18 20:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 20:46 Konrad Rzeszutek Wilk [this message]
2015-12-18 20:46 ` [PATCH RFC] x86: Limit MSR_IA32_THERM_CONTROL and MSR_IA32_ENERGY_PERF_BIAS Konrad Rzeszutek Wilk
2015-12-18 21:31 ` Andrew Cooper
2015-12-21 11:39 ` Jan Beulich
2015-12-21 11:42 ` Jan Beulich
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=1450471606-19129-1-git-send-email-konrad.wilk@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=gang.wei@intel.com \
--cc=ian.campbell@citrix.com \
--cc=keir@xen.org \
--cc=tim@xen.org \
--cc=xen-devel@lists.xenproject.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).