From: Thomas Renninger <trenn@suse.de>
To: Arjan van de Ven <arjan@linux.intel.com>,
linux-pm@lists.linux-foundation.org
Cc: Jean Pihet <jean.pihet@newoldbits.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Len Brown <len.brown@intel.com>,
arjan@infradead.org, Kevin Hilman <khilman@deeprootsystems.com>,
linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org,
linux-perf-users@vger.kernel.org,
linux-trace-users@vger.kernel.org
Subject: Re: [PATCH] tracing, perf: add more power related events
Date: Wed, 22 Sep 2010 19:57:56 +0200 [thread overview]
Message-ID: <201009221957.57845.trenn@suse.de> (raw)
In-Reply-To: <4C9A21AD.1000800@linux.intel.com>
On Wednesday 22 September 2010 17:33:01 Arjan van de Ven wrote:
> On 9/22/2010 8:31 AM, Jean Pihet wrote:
> > Hi,
> >
> > Here is a patch that redefines the power events API. The advantages
> > are: easier maintainance of the kernel and the
> > user space tools, a cleaner and more generic interface, more
> > parameters for fine tracing and even documentation!
> >
> > Thomas, this patch has your patch above merged in ('power-trace: Use
> > power_switch_state instead of power_start and power_end'). The revised
> > ACPI patch is coming asap.
> >
> > The trace points for x86 and OMAP are also udated accordingly.
> >
> > The pytimechart tool needs an update for the new API. This can be done
> > as soon as the kernel code gets merged in.
>
> unfortunately this code is changing a userspace ABI... we really
> shouldn't do that if we can avoid it,
> and here we can avoid it.
Wow, this is your first post on this thread and you needed 1 min, 20 secs
to reply and comment on work that probably took several weeks and which is quite
an improvement.
You did not even start to read the documentation/patch in this minute, did you?
> applications ARE using this stuff!
The current interfaces do not make sense at all.
Things must be changed now before even more ARE using the broken stuff
and things get more complicated.
You should be happy that someone is helping/doing it.
Thomas
next prev parent reply other threads:[~2010-09-22 17:57 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 7:21 [PATCH] tracing, perf: add more power related events 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 [this message]
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-10-04 17:55 ` [linux-pm] " Pavel Machek
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=201009221957.57845.trenn@suse.de \
--to=trenn@suse.de \
--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=linux-omap@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=linux-trace-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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).