All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: cpufreq@www.linux.org.uk
Subject: Re: post-OLS pending cpufreq patches
Date: Wed, 28 Jul 2004 14:59:16 +0100	[thread overview]
Message-ID: <20040728135916.GA6308@redhat.com> (raw)
In-Reply-To: <20040727205126.GB9438@dominikbrodowski.de>

On Tue, Jul 27, 2004 at 10:51:26PM +0200, Dominik Brodowski wrote:

 > As KS and OLS are over, here's a status update on what patches and/or what
 > issues (in the world outside of KS and OLS) are at what state at the moment.
 > Also, I'm looking forward to read Paul's paper in the OLS proceedings, and
 > to see what Dave has added to his TODO list :)

I fly back today (should have been last night, but thats a long
story for another time), and expect to spend a few days doing
nothing work related at all when I get back 8-)

Notes I scribbled in my TODO during OLS include..

- rdmsr_on_cpu(int cpunr)
Paul mentioned this would make life easier in powernow-k8
It's low hanging fruit, as most of the implementation is
already in the msr driver. We can just generic-ise that.

- perform multiple scaling operations to 'step' to driver.
I've had some reports from k7 users that jumps from low->high
still dont work, but gradual increments work. This may also
solve the longhaul problems. k8 also could this I think.

- check permissons on cpufreq sysfs files
Someone mentioned that have these root r-- is a bit
pointless as they aren't really security sensitive.

- fill in gaps between low/high tables
Some powernow-k7 tables only have 2-3 entries in their PST's
though we know from the spec that other frequencies are available.
We could fill in these frequences, and for voltage take value from
next highest.

- no-table support for k7
Recently I've been getting more and more reports from folks putting
mobile K7's into desktop boards, which have no BIOS support
(no PST table, or ACPI P states).
For high speed, take what we booted at.
For low ?
Could be tricky.

- scheduler bits
"migrate everything off this CPU"
Useful when dropping CPU speed to very low speed/power, when
another CPU in the system is not-quite-idle.

- hotplug cpu support?
won't save any power today, but worth thinking about *now*,
as future CPUs could potentially have big savings here.

- longhaul ACPI support ?
Newer systems should support P-states.

- longhaul voltage scaling
I ripped this out long ago. Need to revisit it.


Thanks for scooping up the patches, I'll take a look at merging
them a few days after I get back, possibly the weekend, Monday
at the latest.

		Dave

  reply	other threads:[~2004-07-28 13:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 20:51 post-OLS pending cpufreq patches Dominik Brodowski
2004-07-28 13:59 ` Dave Jones [this message]
2004-07-28 17:25   ` Dominik Brodowski
2004-08-02 19:33 ` Dave Jones
2004-08-02 20:40   ` Dominik Brodowski
2004-08-02 20:42   ` Dominik Brodowski
2004-08-02 20:52     ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2004-08-02 22:45 Pallipadi, Venkatesh
2004-08-03 12:42 ` Dominik Brodowski
2004-08-03 13:17   ` Dave Jones
2004-08-03 13:30     ` Dominik Brodowski
2004-08-03 13:37       ` Dave Jones
2004-08-03 14:07         ` Dominik Brodowski
2004-08-03 14:19           ` Dave Jones
2004-08-03 15:06 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=20040728135916.GA6308@redhat.com \
    --to=davej@redhat.com \
    --cc=cpufreq@www.linux.org.uk \
    /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.