public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mattia Dongili <malattia@linux.it>
To: Guilherme Malschitzky Schroeder <guilherme.m.schroeder@gmail.com>
Cc: linux-kernel@vger.kernel.org, venkatesh.pallipadi@intel.com,
	CPUFreq Mailing List <cpufreq@lists.linux.org.uk>,
	ACPI Devel Mailing List <linux-acpi@vger.kernel.org>
Subject: Re: ACPI regression in 2.6.29 - cpufreq_performance doesn't work
Date: Wed, 11 Feb 2009 15:42:53 +0900	[thread overview]
Message-ID: <20090211064253.GC641@kamineko.org> (raw)
In-Reply-To: <cc0fa41f0902102158y146aa60dmcddbe4c6be2ad56f@mail.gmail.com>

On Wed, Feb 11, 2009 at 03:58:07AM -0200, Guilherme Malschitzky Schroeder wrote:
> On Wed, Feb 11, 2009 at 3:10 AM, Mattia Dongili <malattia@linux.it> wrote:
> > On Wed, Feb 11, 2009 at 12:15:35AM -0200, Guilherme Malschitzky Schroeder wrote:
...
> > Ha! can you check the value for
> > /sys/devices/system/cpu/cpu{0,1}/cpufreq/related_cpus
> > ?

errr... sorry, I meant to say
/sys/devices/system/cpu/cpu{0,1}/cpufreq/affected_cpus

> > or even include the full output of cpufreq-info with both kernels.

anyway from this you can see that there is actually a change
(cpufreq-info reads from affected_cpus and in 2.6.28
sys/.../cpu1/cpufreq should be a link to ../cpu0/cpufreq):

> Here it's:
> 
> 2.6.28.4
...
> # cpufreq-info
> cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
> Report errors and bugs to cpufreq@lists.linux.org.uk, please.
> analyzing CPU 0:
>   driver: acpi-cpufreq
>   CPUs which need to switch frequency at the same time: 0 1
...
> 2.6.29-rc4
...
> # cpufreq-info
> cpufrequtils 004: cpufreq-info (C) Dominik Brodowski 2004-2006
> Report errors and bugs to cpufreq@lists.linux.org.uk, please.
> analyzing CPU 0:
>   driver: acpi-cpufreq
>   CPUs which need to switch frequency at the same time: 0
...
> analyzing CPU 1:
>   driver: acpi-cpufreq
>   CPUs which need to switch frequency at the same time: 1

So I guess you have one of those bioses that prefer sw coordination if
not told to use hw's as explained in the commit message.
And cpufreq-set behaves as it always did ;)

...
> >> >> >> commit d96f94c604453f87fe24154b87e1e9a3a72511f8
> >> >> >> Author: Pallipadi, Venkatesh <venkatesh.pallipadi@intel.com>
> >> >> >> Date:   Mon Feb 2 11:57:18 2009 -0800
> >> >> >>
> >> >> >>     ACPI: Enable bit 11 in _PDC to advertise hw coord
> >> >> >>
> >> >> >>     Bit 11 in intel PDC definitions is meant for OS capability to handle
> >> >> >>     hardware coordination of P-states. In Linux we have always supported
> >> >> >>     hwardware coordination of P-states. Just let the BIOSes know that we
> >> >> >>     support it, by setting this bit.
> >> >> >>
> >> >> >>     Some BIOSes use this bit to choose between hardware or software coordination
> >> >> >>     and without this change below, BIOSes switch to software coordination, which
> >> >> >>     is not very optimal in terms of power consumption and extra
> >> >> >> wakeups from idle.
> >> >> >>
> >> >> >>     Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> >> >> >>     Signed-off-by: Len Brown <len.brown@intel.com>

-- 
mattia
:wq!

      reply	other threads:[~2009-02-11  6:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  3:53 ACPI regression in 2.6.29 - cpufreq_performance doesn't work Guilherme Malschitzky Schroeder
2009-02-10  4:58 ` Mattia Dongili
2009-02-10  6:15   ` Guilherme Malschitzky Schroeder
2009-02-10 11:08     ` Mattia Dongili
     [not found]       ` <cc0fa41f0902101810m77d7054ar7df7b3804cc61e66@mail.gmail.com>
2009-02-11  2:15         ` Guilherme Malschitzky Schroeder
2009-02-11  5:10           ` Mattia Dongili
2009-02-11  5:58             ` Guilherme Malschitzky Schroeder
2009-02-11  6:42               ` Mattia Dongili [this message]

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=20090211064253.GC641@kamineko.org \
    --to=malattia@linux.it \
    --cc=cpufreq@lists.linux.org.uk \
    --cc=guilherme.m.schroeder@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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