From: Randy Dunlap <rdunlap@xenotime.net>
To: venkatesh.pallipadi@intel.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-acpi@vger.kernel.org
Subject: Re: [patch 2/2] x86: Manage ENERGY_PERF_BIAS based on cpufreq governor
Date: Tue, 02 Mar 2010 16:30:49 -0800 [thread overview]
Message-ID: <4B8DADB9.1040302@xenotime.net> (raw)
In-Reply-To: <20100303000849.278509000@intel.com>
On 03/02/10 16:06, venkatesh.pallipadi@intel.com wrote:
{bah, more difficult to review an attachment, so no leading '>'}
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 8c666d8..4945add 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -749,6 +749,10 @@ and is between 256 and 4096 characters. It is defined in the file
Default value is 0.
Value can be changed at runtime via /selinux/enforce.
+ epb [X86] Control IA32_ENERGY_PERF_BIAS setting
+ "disable" - Kernel will not modify this MSR
+ <0..15> - Kernel will set this MSR to i/p static value
+
Should be more like:
epb= [X86] Control IA32_ENERGY_PERF_BIAS setting
Format: { disable | <0...15> }
"disable" - Kernel will not modify this MSR
<0..15> - Kernel will set this MSR to i/p static value
But what is "i/p"? Use whatever word it should be, please.
What do the values mean?
And what does IA32 have to do with this? does it not apply to x86_64?
thanks,
--
~Randy
next prev parent reply other threads:[~2010-03-03 0:30 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 [this message]
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
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=4B8DADB9.1040302@xenotime.net \
--to=rdunlap@xenotime.net \
--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=tglx@linutronix.de \
--cc=venkatesh.pallipadi@intel.com \
/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