From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Colin Cross <ccross@android.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-pm@lists.linux-foundation.org,
Kevin Hilman <khilman@ti.com>, Len Brown <len.brown@intel.com>,
Trinabh Gupta <g.trinabh@gmail.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Deepthi Dharwar <deepthi@linux.vnet.ibm.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Kay Sievers <kay.sievers@vrfy.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [PATCHv2 5/5] cpuidle: coupled: add trace events
Date: Mon, 09 Apr 2012 12:29:20 +0530 [thread overview]
Message-ID: <4F8288C8.50507@ti.com> (raw)
In-Reply-To: <1331749794-8056-6-git-send-email-ccross@android.com>
On Wednesday 14 March 2012 11:59 PM, Colin Cross wrote:
> Adds trace events to allow debugging of coupled cpuidle.
> Can be used to verify cpuidle performance, including time spent
> spinning and time spent in safe states. Not intended for merging.
>
> Signed-off-by: Colin Cross <ccross@android.com>
> ---
I found the trace events quite useful for debug and also to monitor
the cpuidle performance.
I guess we should add these trace events to the core code unless
and until there is a strong reason not to do so.
Regards
Santosh
next prev parent reply other threads:[~2012-04-09 6:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 18:29 [PATCHv2 0/5] coupled cpuidle state support Colin Cross
2012-03-14 18:29 ` [PATCHv2 1/5] cpuidle: refactor out cpuidle_enter_state Colin Cross
2012-03-14 18:29 ` [PATCHv2 2/5] cpuidle: fix error handling in __cpuidle_register_device Colin Cross
2012-03-14 18:29 ` [PATCHv2 3/5] cpuidle: add support for states that affect multiple cpus Colin Cross
2012-03-16 0:04 ` Kevin Hilman
2012-03-16 0:20 ` Colin Cross
2012-03-16 1:52 ` Arjan van de Ven
2012-03-17 12:29 ` Santosh Shilimkar
2012-03-17 19:21 ` Colin Cross
2012-03-18 7:18 ` Shilimkar, Santosh
2012-03-14 18:29 ` [PATCHv2 4/5] cpuidle: coupled: add parallel barrier function Colin Cross
2012-03-14 18:29 ` [PATCHv2 5/5] cpuidle: coupled: add trace events Colin Cross
2012-04-09 6:59 ` Santosh Shilimkar [this message]
2012-03-15 23:37 ` [PATCHv2 0/5] coupled cpuidle state support Colin Cross
2012-03-30 12:53 ` Santosh Shilimkar
2012-04-09 7:11 ` Santosh Shilimkar
2012-04-09 23:35 ` [linux-pm] " Kevin Hilman
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=4F8288C8.50507@ti.com \
--to=santosh.shilimkar@ti.com \
--cc=amit.kucheria@linaro.org \
--cc=arjan@linux.intel.com \
--cc=ccross@android.com \
--cc=daniel.lezcano@linaro.org \
--cc=deepthi@linux.vnet.ibm.com \
--cc=g.trinabh@gmail.com \
--cc=gregkh@suse.de \
--cc=kay.sievers@vrfy.org \
--cc=khilman@ti.com \
--cc=len.brown@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=lorenzo.pieralisi@arm.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;
as well as URLs for NNTP newsgroup(s).