From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
To: Matthew Garrett <mjg@redhat.com>
Cc: Ingo Molnar <mingo@elte.hu>, H Peter Anvin <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>, Len Brown <lenb@kernel.org>,
Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [patch 2/2] x86: Manage ENERGY_PERF_BIAS based on cpufreq governor
Date: Wed, 03 Mar 2010 09:55:38 -0800 [thread overview]
Message-ID: <1267638938.16916.957.camel@localhost.localdomain> (raw)
In-Reply-To: <20100303164007.GA31365@srcf.ucam.org>
On Wed, 2010-03-03 at 08:40 -0800, Matthew Garrett wrote:
> Have you done any measurements with this bit being set dynamically by
> ondemand depending on the target frequency?
>
The not so good part about this feature is that its setting is opaque.
Different CPUs can use this value for different optimizations. So, in
future we may have to change the value of this MSR based on frequency or
other metrics. But, for CPUs which support this MSR today, changing the
value with frequency do not make any difference.
Thanks,
Venki
prev parent reply other threads:[~2010-03-03 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 0:06 [patch 0/2] Support for IA32_ENERGY_PERF_BIAS MSR venkatesh.pallipadi
2010-03-03 0:06 ` [patch 1/2] x86: Look for IA32_ENERGY_PERF_BIAS support venkatesh.pallipadi
2010-03-03 0:06 ` [patch 2/2] x86: Manage ENERGY_PERF_BIAS based on cpufreq governor venkatesh.pallipadi
2010-03-03 0:30 ` Randy Dunlap
2010-03-03 17:52 ` Pallipadi, Venkatesh
2010-03-03 21:57 ` Pavel Machek
2010-03-04 0:27 ` Pallipadi, Venkatesh
2010-03-05 9:19 ` Pavel Machek
2010-03-05 14:36 ` Pallipadi, Venkatesh
2010-03-05 20:40 ` Pavel Machek
2010-03-05 20:55 ` Matthew Garrett
2010-03-05 21:13 ` Pavel Machek
2010-03-05 22:49 ` Matthew Garrett
2010-03-06 6:43 ` Pavel Machek
2010-03-03 16:40 ` Matthew Garrett
2010-03-03 17:55 ` Pallipadi, Venkatesh [this message]
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=1267638938.16916.957.camel@localhost.localdomain \
--to=venkatesh.pallipadi@intel.com \
--cc=davej@redhat.com \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mjg@redhat.com \
--cc=tglx@linutronix.de \
/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