[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <alpine.LFD.2.00.0910051818130.32307@localhost.localdomain>
Date: Mon, 05 Oct 2009 18:20:44 -0400 (EDT)
From: Len Brown <lenb@...nel.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, balbir@...ux.vnet.ibm.com,
torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, a.p.zijlstra@...llo.nl,
shaohua.li@...el.com, svaidy@...ux.vnet.ibm.com
Subject: Re: [git pull request] ACPI Processor Aggregator Driver for 2.6.32-rc1
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists