public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Len Brown <lenb@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Shaohua Li <shaohua.li@intel.com>,
	Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Subject: Re: [git pull request] ACPI Processor Aggregator Driver for 2.6.32-rc1
Date: Sat, 3 Oct 2009 22:49:19 +0200	[thread overview]
Message-ID: <200910032249.19292.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.LFD.2.00.0910030145140.25240@localhost.localdomain>

On Saturday 03 October 2009, Len Brown wrote:
> Hi Linus,
> 
> please pull from: 
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git acpi-pad
> 
> This will add the ACPI Processor Aggregator Driver to the kernel.
> acpi_pad implements a new ACPI feature where the baseboard management
> controller can ask Linux to force busy processors to stay idle.
> 
> The BMC does this under dire electrical or thermal conditions
> after it has already lowered the P-state to low frequencey mode
> on all processors, yet the emergency persists.  This offline
> technique is used before employing even more invasive measures,
> such as taking T-states down to 1/8th of LFM, or powering-off
> the server completely.
> 
> This driver will have no effect on the installed base,
> no no old systems implement this new feature.  However, this
> simle driver in Linux will be useful as this feature
> is deployed by OEMs on new hardware.
> 
> As I mentioned previously, this is an ACPI patch, not a scheduler patch.
> PeterZ is hoping to implement a more sophisticated method for forcing
> idle time in the system with the scheduler, and when that is available,
> I'll be delighted to update this driver to invoke it.
> 
> thanks!
> 
> --
> Len Brown
> Intel Open Source Technology Center
> 
> 
> ps. individual patches are available on linux-acpi@vger.kernel.org
> and a consolidated plain patch is available here:
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/2.6.31/acpi-acpi-pad-20090521-2.6.31-rc4.diff.gz
> 
>  MAINTAINERS             |    8 +
>  drivers/acpi/Kconfig    |   12 +
>  drivers/acpi/Makefile   |    2 +
>  drivers/acpi/acpi_pad.c |  514 +++++++++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 536 insertions(+), 0 deletions(-)
>  create mode 100644 drivers/acpi/acpi_pad.c
> 
> through these commits:
> 
> Len Brown (1):
>       acpi_pad: build only on X86
> 
> Shaohua Li (1):
>       ACPI: create Processor Aggregator Device driver
> 
> with this log:
> 
> commit d91f79ebc3191b15dbe385925af4840f4e68df77
> Author: Len Brown <len.brown@intel.com>
> Date:   Sun Sep 27 02:35:55 2009 -0400
> 
>     acpi_pad: build only on X86
>     
>     X86_FEATURE_MWAIT doesn't exist on ia64...
>     
>     Signed-off-by: Len Brown <len.brown@intel.com>
> 
> commit 8e0af5141ab950b78b3ebbfaded5439dcf8b3a8d
> Author: Shaohua Li <shaohua.li@intel.com>
> Date:   Mon Jul 27 18:11:02 2009 -0400
> 
>     ACPI: create Processor Aggregator Device driver

Can you please point me to the mailing list thread there this driver was
posted (and possibly reviewed and discussed)?

Best,
Rafael

  reply	other threads:[~2009-10-03 20:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-03  5:56 [git pull request] ACPI Processor Aggregator Driver for 2.6.32-rc1 Len Brown
2009-10-03 20:49 ` Rafael J. Wysocki [this message]
2009-10-05  3:32 ` Balbir Singh
2009-10-05  5:33   ` Vaidyanathan Srinivasan
2009-10-05  7:15     ` Balbir Singh
2009-10-05 19:59   ` Rafael J. Wysocki
2009-10-05 20:33     ` Balbir Singh
2009-10-05 20:56     ` Linus Torvalds
2009-10-05 21:51       ` Rafael J. Wysocki
2009-10-05 22:17         ` Len Brown
2009-10-05 21:04     ` Andrew Morton
2009-10-05 22:20       ` Len Brown
2009-10-05 22:40         ` Andrew Morton
2009-10-05 23:23           ` Linus Torvalds
2009-10-06  1:28             ` Len Brown
2009-10-06  9:16               ` Balbir Singh

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=200910032249.19292.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=svaidy@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.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