From: Ross Lagerwall <ross.lagerwall@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Keir Fraser <keir@xen.org>, Xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH 1/2] mwait_idle: Disable Baytrail Core and Module C6 auto-demotion
Date: Mon, 8 Sep 2014 15:02:24 +0100 [thread overview]
Message-ID: <540DB6F0.40204@citrix.com> (raw)
In-Reply-To: <540DC9B20200007800031FDD@mail.emea.novell.com>
On 09/08/2014 02:22 PM, Jan Beulich wrote:
>>>> On 08.09.14 at 14:42, <ross.lagerwall@citrix.com> wrote:
>> From: Len Brown <len.brown@intel.com>
>>
>> Power efficiency improves on Baytrail (Intel Atom Processor E3000)
>> when C6 auto-demotion is disabled.
>>
>> Based on work by Srinidhi Kasagar <srinidhi.kasagar@intel.com>.
>>
>> Signed-off-by: Len Brown <len.brown@intel.com>
>> Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
>
> So we raced on pulling these over - I did so late last week too and
> just didn't get to send them out yet. On this one I in fact doubt
> (and sent a respective query to Len; no response yet) that the MSR
> handling is. Hence my ported over patch is a little different:
>
According to Intel's manual, those two registers have package scope,
i.e. all processor cores in the package share the same MSR, so
presumably the original commit is OK.
--
Ross Lagerwall
next prev parent reply other threads:[~2014-09-08 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 12:42 [PATCH 1/2] mwait_idle: Disable Baytrail Core and Module C6 auto-demotion Ross Lagerwall
2014-09-08 12:42 ` [PATCH 2/2] mwait_idle: Broadwell support Ross Lagerwall
2014-09-08 13:24 ` Jan Beulich
2014-10-16 12:54 ` Chen, Tiejun
2014-10-16 14:06 ` Jan Beulich
2014-10-17 1:22 ` Chen, Tiejun
2014-10-17 8:40 ` Jan Beulich
2014-10-24 3:02 ` Chen, Tiejun
2014-10-17 1:00 ` Chen, Tiejun
2014-09-08 13:22 ` [PATCH 1/2] mwait_idle: Disable Baytrail Core and Module C6 auto-demotion Jan Beulich
2014-09-08 14:02 ` Ross Lagerwall [this message]
2014-09-08 14:20 ` 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=540DB6F0.40204@citrix.com \
--to=ross.lagerwall@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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).