From: "Yury V. Umanets" <umka-nJ1KrdHEGnBBDgjK7y7TUQ@public.gmane.org>
To: christian graf <chr.graf-Mmb7MZpHnFY@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: acpi_processor.c - kernel 2.6.1
Date: Sun, 18 Jan 2004 14:18:48 +0300 [thread overview]
Message-ID: <1074424728.1914.24.camel@firefly> (raw)
In-Reply-To: <1074382993.674.24.camel-GKM3wtwTCu0@public.gmane.org>
On Sun, 2004-01-18 at 02:43, christian graf wrote:
> Hi,
Hello,
>
> reading the /usr/src/linux-2.6.1/drivers/acpi/processor.c
> i thought the kernel should set the state dynamically, based on the
> load. Maybe it is possible to set the processor-state of my centrino
> manually. Can please anybody tell me how to get it right?
>
There is an user-space daemon, which adjusts CPU speed basing on current
loading. And it is able to change CPU frequency if userspace cpufreq
governor is turned on. I would like to see this functionality in kernel
though.
> The reason I'm asking is, that once I do load the processor.ko module,
> my Centrino switches immediately into C2-state. It never switches back
> to C1 state, even under heavy load like compiling the kernel.
>
I guess, that there is no code in kernel, which does watch current
loading and adjust CPU speed. Also this is job for a cpufreq governor,
not for CPU driver.
For now, there are three governors:
(1) powersave -- setting CPU frequency statically to lowest available
frequency.
(2) performance -- setting to highest available frequency.
(3) userspace -- used for setting CPU frequency manually.
Probably there also should be number (4), which will set it basing on
current loading.
> I think the kernel should switch back from C2 to C1 state from alone????
>
> Please ask me whatever you need to help me swtiching back into C1 state.
>
> christian
--
umka
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-18 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 23:43 acpi_processor.c - kernel 2.6.1 christian graf
[not found] ` <1074382993.674.24.camel-GKM3wtwTCu0@public.gmane.org>
2004-01-18 2:58 ` Ducrot Bruno
[not found] ` <20040118025845.GB25416-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-01-18 17:41 ` christian graf
[not found] ` <1074447711.719.13.camel-GKM3wtwTCu0@public.gmane.org>
2004-01-19 9:37 ` Dominik Brodowski
2004-01-18 11:18 ` Yury V. Umanets [this message]
[not found] ` <1074424728.1914.24.camel-YqzrDssuZYw@public.gmane.org>
2004-01-18 13:00 ` Luca Capello
[not found] ` <400A8381.2050607-wlebWZzHoyE@public.gmane.org>
2004-01-18 17:10 ` Mattia Dongili
[not found] ` <20040118171017.GF2375-MEqNC12sBsHxa7XIdbXXog@public.gmane.org>
2004-01-18 18:04 ` Luca Capello
[not found] ` <400ACAC3.1050504-wlebWZzHoyE@public.gmane.org>
2004-01-18 19:28 ` christian graf
2004-01-18 17:39 ` christian graf
2004-01-19 14:10 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2004-01-18 8:14 Yu, Luming
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=1074424728.1914.24.camel@firefly \
--to=umka-nj1krdhegnbbdgjk7y7tuq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=chr.graf-Mmb7MZpHnFY@public.gmane.org \
/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