From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Len Brown <lenb@kernel.org>
Cc: Shaohua Li <shaohua.li@intel.com>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"svaidy@linux.vnet.ibm.com" <svaidy@linux.vnet.ibm.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>,
"andi@firstfloor.org" <andi@firstfloor.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH]new ACPI processor driver to force CPUs idle
Date: Tue, 07 Jul 2009 10:24:54 +0200 [thread overview]
Message-ID: <1246955094.8143.110.camel@twins> (raw)
In-Reply-To: <alpine.LFD.2.00.0906261209370.4148@localhost.localdomain>
On Fri, 2009-06-26 at 12:46 -0400, Len Brown wrote:
> We'd like to ship the forced-idle thread as a self-contained driver,
> if possilbe. Because that would enable us to easily back-port it
> to some enterprise releases that want the feature. So if we can
> implement this such that it is functional with existing scheduler
> facilities, that would be get us by. If the scheduler evolves
> and provides a more optimal mechanism in the future, then that is
> great, as long as we don't have to wait for that to provide
> the basic version of the feature.
I don't think we should ever merge anything because of backports for
stale kernels.
If you want it in enterprise stuff all you need is something upstream,
and that something should be the scheduler driven bits.
After that you can argue the full backport isn't possible (should be
quite easy given that enterprise kernels still think kABI is something
sane) and propose this hack for them.
next prev parent reply other threads:[~2009-07-07 8:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 4:13 [PATCH]new ACPI processor driver to force CPUs idle Shaohua Li
2009-06-24 6:39 ` Peter Zijlstra
2009-06-24 7:47 ` Shaohua Li
2009-06-24 8:03 ` Peter Zijlstra
2009-06-24 8:21 ` Shaohua Li
2009-06-26 18:16 ` Vaidyanathan Srinivasan
2009-06-29 2:54 ` Shaohua Li
2009-07-06 18:03 ` Vaidyanathan Srinivasan
2009-07-06 23:43 ` Andi Kleen
2009-07-07 0:50 ` Pallipadi, Venkatesh
2009-07-10 19:31 ` Len Brown
2009-06-24 17:20 ` Len Brown
2009-06-26 7:46 ` Peter Zijlstra
2009-06-26 16:46 ` Len Brown
2009-06-26 18:42 ` Vaidyanathan Srinivasan
2009-07-10 19:47 ` Len Brown
2009-06-26 19:49 ` Matthew Garrett
2009-07-10 20:29 ` Len Brown
2009-06-30 8:02 ` Shaohua Li
2009-07-07 8:26 ` Peter Zijlstra
2009-07-07 8:24 ` Peter Zijlstra [this message]
2009-07-10 20:41 ` Len Brown
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=1246955094.8143.110.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shaohua.li@intel.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--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