From: Nishanth Menon <nm@ti.com>
To: jean.pihet@newoldbits.com
Cc: mingo@elte.hu, linux-kernel@vger.kernel.org, trenn@suse.de,
linux-omap@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>,
linux-perf-users@vger.kernel.org, rjw@sisk.pl,
Jean Pihet <j-pihet@ti.com>
Subject: Re: [PATCH 2/3] perf: add OMAP support for the new power events
Date: Tue, 04 Jan 2011 12:03:56 -0600 [thread overview]
Message-ID: <4D23610C.1060009@ti.com> (raw)
In-Reply-To: <1294136263-24020-3-git-send-email-j-pihet@ti.com>
jean.pihet@newoldbits.com had written, on 01/04/2011 04:17 AM, the
following:
[..]
> diff --git a/arch/arm/mach-omap2/pm34xx.c b/arch/arm/mach-omap2/pm34xx.c
> index 0ec8a04..0ee0b0e 100644
> --- a/arch/arm/mach-omap2/pm34xx.c
> +++ b/arch/arm/mach-omap2/pm34xx.c
> @@ -29,6 +29,7 @@
> #include <linux/delay.h>
> #include <linux/slab.h>
> #include <linux/console.h>
> +#include <trace/events/power.h>
>
> #include <plat/sram.h>
> #include <plat/clockdomain.h>
> @@ -506,8 +507,14 @@ static void omap3_pm_idle(void)
> if (omap_irq_pending() || need_resched())
> goto out;
>
> + trace_power_start(POWER_CSTATE, 1, smp_processor_id());
> + trace_cpu_idle(1, smp_processor_id());
> +
> omap_sram_idle();
>
> + trace_power_end(smp_processor_id());
> + trace_cpu_idle(PWR_EVENT_EXIT, smp_processor_id());
Dumb question: it just tells me which C state was attempted - not if
actually succeeded in hitting it rt? Does'nt this give us a false data?
[..]
> diff --git a/arch/arm/plat-omap/clock.c b/arch/arm/plat-omap/clock.c
> index fc62fb5..7cbb09b 100644
> --- a/arch/arm/plat-omap/clock.c
> +++ b/arch/arm/plat-omap/clock.c
(from an offline discussion on a related topic): Would it also be nice
to hook on mach-omap2/clock.c points as well to hook on indirect changes?
[..]
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2011-01-04 18:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 10:17 [PATCH 0/3] perf, tools: new power trace API jean.pihet
2011-01-04 10:17 ` [PATCH 1/3] perf: add calls to suspend trace point jean.pihet
2011-01-04 10:39 ` Ingo Molnar
2011-01-04 10:17 ` [PATCH 2/3] perf: add OMAP support for the new power events jean.pihet
2011-01-04 10:42 ` Ingo Molnar
2011-01-04 10:58 ` Pihet-XID, Jean
2011-01-04 18:03 ` Nishanth Menon [this message]
2011-01-05 10:56 ` Jean Pihet
2011-01-04 10:17 ` [PATCH 3/3] tools, perf: Documentation for the power events API jean.pihet
2011-01-04 10:48 ` [PATCH 1/3] perf: add calls to suspend trace point jean.pihet
2011-01-04 11:29 ` Pavel Machek
2011-01-04 15:00 ` Jean Pihet
2011-01-04 23:01 ` Rafael J. Wysocki
2011-01-05 10:09 ` Jean Pihet
2011-01-05 10:15 ` Rafael J. Wysocki
2011-01-05 11:23 ` Pavel Machek
2011-01-04 10:54 ` [PATCH 2/3] perf: add OMAP support for the new power events jean.pihet
2011-01-04 18:48 ` Paul Walmsley
2011-01-05 11:05 ` Jean Pihet
2011-01-10 14:14 ` Thomas Renninger
2011-01-11 1:24 ` Kevin Hilman
2011-01-10 19:06 ` Paul Walmsley
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=4D23610C.1060009@ti.com \
--to=nm@ti.com \
--cc=arjan@linux.intel.com \
--cc=j-pihet@ti.com \
--cc=jean.pihet@newoldbits.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=trenn@suse.de \
/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).