public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: christian graf <chr.graf-Mmb7MZpHnFY@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@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 18:41:51 +0100	[thread overview]
Message-ID: <1074447711.719.13.camel@dragon> (raw)
In-Reply-To: <20040118025845.GB25416-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>

Hi Bruno,

I thought for full performance the C1 state is better as the C2 (which
keeps good performance as well as powersavings)? Or why do you prefer
C2?

How can I avoid the bios - trouble?

christian

 
Am So, den 18.01.2004 schrieb Ducrot Bruno um 03:58:
> On Sun, Jan 18, 2004 at 12:43:13AM +0100, christian graf wrote:
> > Hi,
> > 
> > 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?
> > 
> > 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 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
> > 
> > 
> > 
> > cat /proc/acpi/processor/CPU0/power
> > active state:            C2
> > default state:           C1
> > bus master activity:     ffffffff
> > states:
> >     C1:                  promotion[C2] demotion[--] latency[000]
> > usage[00000010]
> >    *C2:                  promotion[C3] demotion[C1] latency[001]
> > usage[00905291]
> >     C3:                  promotion[--] demotion[C2] latency[185]
> > usage[00000000]
> > 
> 
> The latency for C2 is too low (and therefore it is a BIOS trouble).
> Anyway, C2 is better than C1, so you want C2 ;)
> 
> Note that there is some missing code in the processor.c stuff, which may
> give you more appropriate latency, and a C4 state.  The code for is under
> developpement.



-------------------------------------------------------
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

  parent reply	other threads:[~2004-01-18 17:41 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 [this message]
     [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
     [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=1074447711.719.13.camel@dragon \
    --to=chr.graf-mmb7mzphnfy@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@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