From: Peter Zijlstra <peterz@infradead.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: 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>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH V5 2/2] tracing, perf : add cpu hotplug trace events
Date: Thu, 24 Feb 2011 18:46:37 +0000 [thread overview]
Message-ID: <1298573197.2428.457.camel@twins> (raw)
In-Reply-To: <AANLkTinkctQ6Nek98JV7vaos34gD4Qn8nsuBzt=_Jj6T@mail.gmail.com>
On Thu, 2011-02-24 at 18:33 +0100, Vincent Guittot wrote:
> The goal is to measure the latency of each part (kernel, architecture)
> and also to trace the cpu hotplug activity with other power events. I
> have tested these traces events on an arm platform.
> this patch adds new events for cpu hotplug tracing
> * plug/unplug sequence
> * core and architecture latency measurements
Aside of the points tglx made, I do have to ask _WHY_!?
Anybody who is interested in the latency of cpu hotplug is deluding
himself, also cpu hotplug is _NOT_ a power management feature, so the
rest of your justification just disappeared as well.
next prev parent reply other threads:[~2011-02-24 18:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 17:33 [PATCH V5 2/2] tracing, perf : add cpu hotplug trace events 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 [this message]
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
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=1298573197.2428.457.camel@twins \
--to=peterz@infradead.org \
--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=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;
as well as URLs for NNTP newsgroup(s).