From: Len Brown <len.brown@intel.com>
To: Dave Jones <davej@redhat.com>
Cc: "cpufreq@www.linux.org.uk" <cpufreq@www.linux.org.uk>
Subject: Re: ACPI / CPUFREQ.
Date: 03 Aug 2004 11:41:28 -0400 [thread overview]
Message-ID: <1091547688.3473.4.camel@dhcppc4> (raw)
In-Reply-To: <20040803151010.GQ12724@redhat.com>
On Tue, 2004-08-03 at 11:10, Dave Jones wrote:
> At his ACPI talk at OLS, Len mentioned that it would be beneficial
> to have ACPI and CPUFREQ working together a little better.
>
> Len, care to kick off some thoughts on what pieces you had in mind ?
>
> The biggest problem is probably ACPI thinking the CPU should be at a
> certain P-state whilst the user has forced it to another with cpufreq.
I think there are 2 major issues.
1. confusion about best driver to use
this, of course, should be automatic
and should not depend on if the drivers
are built-in or modules.
2. no coordination between P-states
and T-states. ACPI currently kicks
in throttling upon high temperature conditions,
but it doesn't make sense to use throttling
unless we're already in the most power-conserving
P-state available.
-Len
next prev parent reply other threads:[~2004-08-03 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-03 15:10 ACPI / CPUFREQ Dave Jones
2004-08-03 15:41 ` Len Brown [this message]
2004-08-03 20:51 ` Dominik Brodowski
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=1091547688.3473.4.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=cpufreq@www.linux.org.uk \
--cc=davej@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.