From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: acme@redhat.com, vincent.weaver@maine.edu,
Vince Weaver <vince@deater.net>,
Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, paulus@samba.org,
xiaoguangrong@linux.vnet.ibm.com,
Runzhen Wang <runzhen@linux.vnet.ibm.com>,
sukadev@linux.vnet.ibm.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 2/2] perf tools: Make Power7 events available for perf
Date: Fri, 5 Jul 2013 12:23:02 +0200 [thread overview]
Message-ID: <20130705102302.GA10227@gmail.com> (raw)
In-Reply-To: <20130704125700.GM18898@dyad.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, Jul 04, 2013 at 10:52:18PM +1000, Michael Ellerman wrote:
> > I don't think it even needs libpfm4, just some csv files in tools/perf
> > would do the trick.
>
> Right; I think Stephane and Jiri are in favour of creating a 'new'
> project that includes just the event definitions in a plain text format
> and a little library with parser to be used by all interested parties.
I'd be fine with that if it's stuck somewhere into tools/lib/ or so.
Thanks,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Michael Ellerman <michael@ellerman.id.au>,
Vince Weaver <vince@deater.net>,
Runzhen Wang <runzhen@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
paulus@samba.org, acme@redhat.com, vincent.weaver@maine.edu,
Stephane Eranian <eranian@google.com>,
sukadev@linux.vnet.ibm.com, xiaoguangrong@linux.vnet.ibm.com
Subject: Re: [PATCH v2 2/2] perf tools: Make Power7 events available for perf
Date: Fri, 5 Jul 2013 12:23:02 +0200 [thread overview]
Message-ID: <20130705102302.GA10227@gmail.com> (raw)
In-Reply-To: <20130704125700.GM18898@dyad.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Thu, Jul 04, 2013 at 10:52:18PM +1000, Michael Ellerman wrote:
> > I don't think it even needs libpfm4, just some csv files in tools/perf
> > would do the trick.
>
> Right; I think Stephane and Jiri are in favour of creating a 'new'
> project that includes just the event definitions in a plain text format
> and a little library with parser to be used by all interested parties.
I'd be fine with that if it's stuck somewhere into tools/lib/ or so.
Thanks,
Ingo
next prev parent reply other threads:[~2013-07-05 10:23 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 14:35 [PATCH v2 0/2] perf tools: Power7 events name available for perf Runzhen Wang
2013-06-25 14:35 ` Runzhen Wang
2013-06-25 14:35 ` [PATCH v3 1/2] perf tools: fix a typo of a Power7 event name Runzhen Wang
2013-06-25 14:35 ` Runzhen Wang
2013-06-27 14:26 ` Michael Ellerman
2013-06-27 14:26 ` Michael Ellerman
2013-06-25 14:35 ` [PATCH v2 2/2] perf tools: Make Power7 events available for perf Runzhen Wang
2013-06-25 14:35 ` Runzhen Wang
2013-06-25 16:46 ` Vince Weaver
2013-06-25 16:46 ` Vince Weaver
2013-07-04 12:52 ` Michael Ellerman
2013-07-04 12:52 ` Michael Ellerman
2013-07-04 12:57 ` Peter Zijlstra
2013-07-04 12:57 ` Peter Zijlstra
2013-07-05 10:23 ` Ingo Molnar [this message]
2013-07-05 10:23 ` Ingo Molnar
2013-07-09 1:29 ` Michael Ellerman
2013-07-09 1:29 ` Michael Ellerman
2013-07-09 2:24 ` Vince Weaver
2013-07-09 2:24 ` Vince Weaver
2013-07-09 3:34 ` Michael Ellerman
2013-07-09 3:34 ` Michael Ellerman
2013-07-09 15:20 ` Vince Weaver
2013-07-09 15:20 ` Vince Weaver
2013-07-10 2:37 ` Michael Ellerman
2013-07-10 2:37 ` Michael Ellerman
2013-07-09 8:14 ` Peter Zijlstra
2013-07-09 8:14 ` Peter Zijlstra
2013-07-09 15:05 ` Vince Weaver
2013-07-09 15:05 ` Vince Weaver
2013-07-11 10:58 ` Will Deacon
2013-07-11 10:58 ` Will Deacon
2013-07-11 17:53 ` Vince Weaver
2013-07-11 17:53 ` Vince Weaver
2013-07-10 3:09 ` Michael Ellerman
2013-07-10 3:09 ` Michael Ellerman
2013-07-10 8:34 ` Ingo Molnar
2013-07-10 8:34 ` Ingo Molnar
2013-07-11 4:42 ` Vince Weaver
2013-07-11 4:42 ` Vince Weaver
2013-07-11 6:58 ` Michael Ellerman
2013-07-11 6:58 ` Michael Ellerman
2013-06-27 14:23 ` Michael Ellerman
2013-06-27 14:23 ` Michael Ellerman
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=20130705102302.GA10227@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=runzhen@linux.vnet.ibm.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=vince@deater.net \
--cc=vincent.weaver@maine.edu \
--cc=xiaoguangrong@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.