public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.org>
To: Dave Jones <davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Cc: Venkatesh Pallipadi
	<venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	cpufreq <cpufreq-1walMZg8u8rXmaaqVzeoHQ@public.gmane.org>,
	acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	Rajesh Shah <rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [RFC][PATCH 0/4] Software coordination of frequency across CPUs sharing common P-state
Date: Thu, 1 Sep 2005 11:08:22 +0200	[thread overview]
Message-ID: <20050901090822.GD6285@isilmar.linta.de> (raw)
In-Reply-To: <20050901052903.GA17927-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>

On Thu, Sep 01, 2005 at 01:29:03AM -0400, Dave Jones wrote:
> On Wed, Aug 31, 2005 at 02:09:33PM -0700, Venkatesh Pallipadi wrote:
> 
>  > ACPI 3.0 (http://www.acpi.info) adds new methods with which BIOS can communicate
>  > P-state dependency domains (List of CPUs that share a common P-state) to
>  > the OS. This can be used in conjunction with the existing "cpu group awareness"
>  > in cpufreq infrastructure, to manage the group of CPUs sharing the common 
>  > P-state, in a better way.
>  > 
>  > The patchset that follows adds this "software-coordination" feature in 
>  > acpi-perflib, and also changes acpi-cpufreq and speedstep-centrino drivers to
>  > use this feature. 
> 
> Patch 1 rejects against the latest git tree, due to Len's latest ACPI changes.
> That (and possibly patch 4) need redoing.
> 
> From a first look, these patches look ok to me, so if you rediff these,
> and Len is happy with the ACPI changes, I'm happy to merge them for 2.6.14

Patches

Acked-by: Dominik Brodowski <linux-X3ehHDuj6sIIGcDfoQAp7OTW4wlIGRCZ@public.gmane.org>

Nice work!

	Dominik


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

      parent reply	other threads:[~2005-09-01  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 21:09 [RFC][PATCH 0/4] Software coordination of frequency across CPUs sharing common P-state Venkatesh Pallipadi
     [not found] ` <20050831140933.A12497-39QZ/XbsZ5/mO6KZMuUCQVaTQe2KTcn/@public.gmane.org>
2005-09-01  5:29   ` Dave Jones
     [not found]     ` <20050901052903.GA17927-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2005-09-01  9:08       ` Dominik Brodowski [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=20050901090822.GD6285@isilmar.linta.de \
    --to=linux-x3ehhduj6siigcdfoqap7otw4wligrcz@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=cpufreq-1walMZg8u8rXmaaqVzeoHQ@public.gmane.org \
    --cc=davej-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
    --cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=rajesh.shah-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@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