From: Jiri Olsa <jolsa@redhat.com>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
Corey Ashford <cjashfor@linux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Namhyung Kim <namhyung@kernel.org>,
David Ahern <dsahern@gmail.com>
Subject: Re: [RFC 0/4] perf tools: Remove event types data
Date: Wed, 10 Jul 2013 09:49:40 +0200 [thread overview]
Message-ID: <20130710074940.GA1048@krava.brq.redhat.com> (raw)
In-Reply-To: <1500509.qlU7PPnHQq@hammer82.arch.suse.de>
On Wed, Jul 10, 2013 at 08:11:48AM +0200, Thomas Renninger wrote:
> On Tuesday, July 09, 2013 06:48:55 PM Jiri Olsa wrote:
> > hi,
> > following up on the 'perf timechart' FIXME note and changing
> > its tracepoint match not to use event types data.
>
> Looks sane and pretty straight forward.
> Still I am not that deep involved in perf to give a Reviewed-by: quickly...
thanks, I saw your name in changelog.. wanted to include
someone who probably uses timechart command ;-)
>
> #define SUPPORT_OLD_POWER_EVENTS
> could also vanish, maybe with the next round.
ok
jirka
next prev parent reply other threads:[~2013-07-10 7:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 16:48 [RFC 0/4] perf tools: Remove event types data Jiri Olsa
2013-07-09 16:48 ` [PATCH 1/4] perf tools: Remove event types framework only user Jiri Olsa
2013-07-11 6:16 ` Namhyung Kim
2013-07-11 12:26 ` Jiri Olsa
2013-07-09 16:48 ` [PATCH 2/4] perf tools: Remove event types from perf data file Jiri Olsa
2013-07-09 16:48 ` [PATCH 3/4] perf tools: Remove event types pushing from record command Jiri Olsa
2013-07-09 16:48 ` [PATCH 4/4] perf tools: Remove event types framework completely Jiri Olsa
2013-07-09 20:49 ` [RFC 0/4] perf tools: Remove event types data Jiri Olsa
2013-07-10 6:11 ` Thomas Renninger
2013-07-10 7:49 ` Jiri Olsa [this message]
2013-07-15 19:11 ` Arnaldo Carvalho de Melo
2013-07-11 6:19 ` Namhyung Kim
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=20130710074940.GA1048@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).