From: Pavel Machek <pavel@ucw.cz>
To: Matthew Garrett <mjg@redhat.com>
Cc: "Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
Randy Dunlap <rdunlap@xenotime.net>, 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: Fri, 5 Mar 2010 22:13:30 +0100 [thread overview]
Message-ID: <20100305211329.GC20554@elf.ucw.cz> (raw)
In-Reply-To: <20100305205522.GA15489@srcf.ucam.org>
On Fri 2010-03-05 20:55:22, Matthew Garrett wrote:
> On Fri, Mar 05, 2010 at 09:40:29PM +0100, Pavel Machek wrote:
>
> > That can be only true if it does not give benefits period... AC and
> > battery power are quite different scenarios.
>
> No, they're not.
Yes, they are.
Would you care to elaborate? I may very well want top power on AC
power, and max powersavings on battery; most people do.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2010-03-05 21:13 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 [this message]
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=20100305211329.GC20554@elf.ucw.cz \
--to=pavel@ucw.cz \
--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=rdunlap@xenotime.net \
--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