From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Nicolas Pitre <nicolas.pitre@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Vincent Guittot <vincent.guittot@linaro.org>,
lkml <linux-kernel@vger.kernel.org>,
linux-hotplug@vger.kernel.org,
Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
amit.kucheria@linaro.org, Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH V5 2/2] tracing, perf : add cpu hotplug trace events
Date: Thu, 24 Feb 2011 20:40:11 +0000 [thread overview]
Message-ID: <20110224204011.5985cf63@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <1298579452.5226.834.camel@laptop>
On Thu, 24 Feb 2011 21:30:52 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, 2011-02-24 at 15:24 -0500, Nicolas Pitre wrote:
>
> > Most SMP ARM processors are going to use it soon. Powering down idle
> > cores provides substantial power saving.
And some X86 will be doing likewise
> And why can't regular idle paths be used? CPU hotplug is a massively
> expensive operation.
They are not CPU idling on our idle path, they are dropping into suspend
to RAM, that means they need to drop the devices into S2R states as well.
And yes the paths are currently expensive in places but they need to be
sped up more not messed up. For most devices it's not going to be that
hard to sort out - the big ugly is x86 patching the instruction stream
back and forth each suspend/resume which is in "durrr..." category of
smartness.
next prev parent reply other threads:[~2011-02-24 20:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 17:33 Vincent Guittot
2011-02-24 18:40 ` Thomas Gleixner
2011-02-28 13:36 ` Vincent Guittot
2011-03-02 10:08 ` Thomas Gleixner
2011-03-02 19:02 ` Vincent Guittot
2011-03-02 21:12 ` Thomas Gleixner
2011-02-24 18:46 ` Peter Zijlstra
2011-02-24 20:11 ` Alan Cox
2011-02-24 20:16 ` Thomas Gleixner
2011-02-24 20:24 ` Nicolas Pitre
2011-02-24 20:30 ` Peter Zijlstra
2011-02-24 20:40 ` Alan Cox [this message]
2011-02-24 20:40 ` Nicolas Pitre
2011-02-24 20:49 ` Peter Zijlstra
2011-02-24 20:49 ` Thomas Gleixner
2011-02-24 21:04 ` Alan Cox
2011-02-24 21:12 ` Thomas Gleixner
2011-02-24 21:17 ` Peter Zijlstra
2011-02-24 21:33 ` Thomas Gleixner
2011-02-24 20:47 ` Thomas Gleixner
2011-02-24 20:58 ` Peter Zijlstra
2011-02-24 21:03 ` Thomas Gleixner
2011-02-24 21:11 ` Paul E. McKenney
2011-02-24 20:27 ` Peter Zijlstra
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=20110224204011.5985cf63@lxorguk.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=amit.kucheria@linaro.org \
--cc=fweisbec@gmail.com \
--cc=linux-hotplug@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nicolas.pitre@linaro.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®