public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Thomas Renninger <trenn@suse.de>
Cc: Jean Pihet <jean.pihet@newoldbits.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Len Brown <len.brown@intel.com>,
	Arjan Van De Ven <arjan@linux.intel.com>,
	arjan@infradead.org, Kevin Hilman <khilman@deeprootsystems.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tracing, perf: add more power related events
Date: Fri, 3 Sep 2010 22:28:39 +0200	[thread overview]
Message-ID: <20100903202839.GA8679@elte.hu> (raw)
In-Reply-To: <201009032210.08524.trenn@suse.de>


* Thomas Renninger <trenn@suse.de> wrote:

> On Friday 03 September 2010 21:55:55 Ingo Molnar wrote:
> > 
> > * Thomas Renninger <trenn@suse.de> wrote:
> > 
> > > Hi Jean,
> > > 
> > > Summary at the beginning if people stop reading on the details
> > > below...:
> > > Nice work!
> > > You have my vote to get this merged.
> > > I think it's up to Ingo to push it.
> > 
> > Well, the patch that got posted:
> > 
> >   [PATCH] tracing, perf: add more power related events
> > 
> > Only adds tracepoints to power.h, but doesnt actually use them anywhere 
> > ...
> > 
> > Is there a companion patch i missed?
> Yep.
> Jean has nicely made up a tiny website he refered to in his mail:
> http://www.omappedia.com/wiki/Power_Management_Debug_and_Profiling

Ah, that wasnt in the first patch. (Please re-start discussion threads 
when something is re-submitted)

Nice website. Looks like these new tracepoints are really useful.

> There he shows the whole big patch and states:

Generally it's nice to post patches to lkml too, so that people have 
something to discuss.

> Since the patch touches generic files (in include/trace/events/power.h), it is split in parts:
>     * generic code: submitted to the LKML, cf. http://marc.info/?l=linux-kernel&m=128195697205096&w=4 ,
>     * ARM/OMAP specific code for the already existing events: to be submitted to l-o, cf. http://www.spinics.net/lists/linux-omap/msg35357.html,
>     * ARM/OMAP specific code for the new events, to be submitted once the generic code is accepted. 
> 
> > Also, it would be nice to add it to x86 and to OMAP at once, and 
> > synchronize up all the power events
>
> I can add sleep state events to x86 acpi parts, but even these are, as 
> said, not that interesting as they might be on ARM ultra mobile use 
> cases.

Yeah - but as long as they are at least attempted to be cross-platform, 
that would be fine. The ACPI folks are Cc:-ed so they can object if they 
dont like something.

> > - and check how existing tools like 
> > powertop make use of such events - and sync it all up.
>
> Does powertop use these events?

It certainly does quite a few things wrt. power usage analysis. Arjan is 
on the Cc:, maybe he has an opinion about these tracepoints.

> > We dont want to have inconsistent, architecture-dependent events in 
> > the end, for obvious reasons.
>
> Jean also shows screenshots at the link above
> how perf timechart or the the corresponding
> gui app PyTimechart still works together with these.
> I can't see how the new events should break an existing app, they should
> just ignore events they are not aware of.

Yeah, extensions rarely break anything. What i mentioned was 
'inconsistent, architecture-dependent events', which is not a fact but a 
possible danger: as these new events are only for OMAP right now. They 
might be OK, they might be not OK - i dont know, that's why i suggested 
to make them cross-platform in practice too.

So it would be nice to get some feedback from the ACPI folks - but if 
you guys can also do an ACPI patch that would be even better!

Thanks,

	Ingo

  reply	other threads:[~2010-09-03 20:28 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16 11:09 [PATCH] tracing, perf: add more power related events Jean Pihet
2010-08-16 11:15 ` Peter Zijlstra
2010-08-16 11:25   ` Jean Pihet
2010-08-23 10:25     ` Jean Pihet
2010-09-03 17:00       ` Jean Pihet
2010-09-03 18:05         ` Thomas Renninger
2010-09-03 19:55           ` Ingo Molnar
2010-09-03 20:10             ` Thomas Renninger
2010-09-03 20:28               ` Ingo Molnar [this message]
2010-09-03 22:56               ` Arjan van de Ven
2010-09-04  8:18                 ` Ingo Molnar
2010-09-06  8:56                   ` Jean Pihet
2010-09-06 10:42                     ` Thomas Renninger
2010-09-06 11:27                       ` Jean Pihet
2010-09-06 12:00                         ` Thomas Renninger
2010-09-07  7:28                           ` Jean Pihet
  -- strict thread matches above, loose matches on Subject: below --
2010-09-07  7:21 Jean Pihet
2010-09-07  8:01 ` Jean Pihet
2010-09-08  6:53 ` Ingo Molnar
2010-09-09  7:15   ` Jean Pihet
2010-09-09  7:54     ` Ingo Molnar
2010-09-15 15:45       ` Jean Pihet
2010-09-17 13:08         ` Thomas Renninger
2010-09-17 14:05           ` Jean Pihet
2010-09-17 14:24             ` Ingo Molnar
2010-09-17 15:36               ` Thomas Renninger
2010-09-17 16:24                 ` Ingo Molnar
2010-09-17 22:26                   ` Thomas Renninger
2010-09-22 15:31                     ` Jean Pihet
2010-09-22 15:33                       ` Arjan van de Ven
2010-09-22 15:36                         ` Jean Pihet
2010-09-22 16:32                           ` Arjan van de Ven
2010-09-22 16:43                             ` Peter Zijlstra
2010-09-22 17:06                               ` Arjan van de Ven
2010-09-22 17:30                                 ` Peter Zijlstra
2010-09-22 18:15                                   ` Steven Rostedt
2010-09-22 18:23                                     ` Ingo Molnar
2010-09-22 18:30                                       ` Peter Zijlstra
2010-09-22 18:26                                     ` Peter Zijlstra
2010-09-22 18:36                                       ` Steven Rostedt
2010-09-22 18:43                                         ` Peter Zijlstra
2010-09-22 19:14                                       ` Frank Ch. Eigler
2010-09-22 17:36                                 ` Thomas Renninger
2010-09-22 16:47                             ` Peter Zijlstra
2010-09-22 17:57                         ` Thomas Renninger
2010-09-22 18:13                           ` Arjan van de Ven
2010-09-22 18:34                             ` Thomas Renninger
2010-09-22 18:09                         ` Rafael J. Wysocki
2010-09-22 18:49                       ` Rafael J. Wysocki
2010-09-28  8:35                         ` Jean Pihet
2010-09-28 21:22                           ` Rafael J. Wysocki
2010-09-28 21:43                             ` Jean Pihet
2010-09-28 22:05                               ` Rafael J. Wysocki
2010-09-28 21:45                             ` Arjan van de Ven
2010-09-28 22:05                               ` Rafael J. Wysocki
2010-09-29  7:49                               ` Thomas Renninger
2010-09-29  9:25                                 ` Jean Pihet
2010-09-17 15:29             ` Thomas Renninger
2010-09-17 21:58             ` Thomas Renninger
2010-09-17 22:04             ` Thomas Renninger
2010-09-17 22:10             ` Thomas Renninger
2010-09-17 22:17             ` Thomas Renninger

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=20100903202839.GA8679@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=arjan@linux.intel.com \
    --cc=jean.pihet@newoldbits.com \
    --cc=khilman@deeprootsystems.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --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