From: Len Brown <lenb@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
balbir@linux.vnet.ibm.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
a.p.zijlstra@chello.nl, shaohua.li@intel.com,
svaidy@linux.vnet.ibm.com
Subject: Re: [git pull request] ACPI Processor Aggregator Driver for 2.6.32-rc1
Date: Mon, 05 Oct 2009 18:20:44 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0910051818130.32307@localhost.localdomain> (raw)
In-Reply-To: <20091005140415.57f1db5e.akpm@linux-foundation.org>
> Technical question: the overall feature, which I'd describe as
> "shutting down CPUs when an external agent tells us the
> thermal/electrical/other load is too high" is not at all specific to
> the x86 CPU. Should the code have been designed in such a way as to
> permit other architectures to play?
I agree with Peter and Vaidy that a generic capability in the Linux
scheduler would be wonderful. But we don't have that today.
Re: this driver in particular...
acpi_pad accepts an ACPI event from the platform and then
does something with it.
Today, ACPI runs on just x86 and ia64, and I'm not aware
of any plans to implement this particularly feature on ia64 platforms.
cheers,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2009-10-05 22:20 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
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 [this message]
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=alpine.LFD.2.00.0910051818130.32307@localhost.localdomain \
--to=lenb@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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