From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@redhat.com>
Cc: acme@kernel.org, jolsa@redhat.com, namhyung@kernel.org,
eranian@google.com, linux-kernel@vger.kernel.org,
mingo@kernel.org
Subject: Re: More updates for event lists in perf list
Date: Sun, 31 May 2015 20:33:10 -0700 [thread overview]
Message-ID: <20150601033310.GA1503@us.ibm.com> (raw)
In-Reply-To: <1433088696-15491-1-git-send-email-andi@firstfloor.org>
Andi Kleen [andi@firstfloor.org] wrote:
| This adds support for the event topics that Ingo requested, and
| replaces the earlier event group patch. JSON files now have a Topic
| header that is used by perf list to group events.
|
| This applies on top of Sukadev's patchkit. In addition
| the Intel events also need to be pulled from
|
| git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git perf/intel-json-files-3
I addressed comments, rebased to Arnaldo's tree and pushed all patches to:
https://github.com/sukadev/linux.git
Branches:
json-v12 (code only)
json-files-3 (x86 and powerpc data files only)
Please let me know if they work for you. I will email the patches for
the code in a day or so.
Sukadev
next prev parent reply other threads:[~2015-06-01 3:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-31 16:11 More updates for event lists in perf list Andi Kleen
2015-05-31 16:11 ` [PATCH 1/3] perf, tools: Add override support for event list CPUID Andi Kleen
2015-06-01 10:29 ` Jiri Olsa
2015-05-31 16:11 ` [PATCH 2/3] perf, tools: Support long descriptions with perf list -v Andi Kleen
2015-05-31 16:11 ` [PATCH 3/3] perf, tools: Add support for event list topics Andi Kleen
2015-06-01 3:33 ` Sukadev Bhattiprolu [this message]
2015-06-01 8:52 ` More updates for event lists in perf list Jiri Olsa
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=20150601033310.GA1503@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.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 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.