public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: sukadev@linux.vnet.ibm.com
Cc: jolsa@redhat.com, acme@kernel.org, namhyung@kernel.org,
	linux-kernel@vger.kernel.org
Subject: perf, tools: Event files for Intel x86
Date: Wed, 20 May 2015 21:11:27 -0700	[thread overview]
Message-ID: <1432181493-18743-1-git-send-email-andi@firstfloor.org> (raw)

This patchkit extends Sukadev builtin event list patches for Intel x86.
With that perf can build in event lists.

This also adds some missing features from the older JSON patchkits,
in particular the ability to print descriptions.

I am not posting the actual event files, because they are gigantic
(several MB) but you can get them from git here:

git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc.git perf/builtion-json-1

Currently only core events are included, not uncore.

-Andi



             reply	other threads:[~2015-05-21  4:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  4:11 Andi Kleen [this message]
2015-05-21  4:11 ` [PATCH 1/6] perf, tools: Handle header line in mapfile Andi Kleen
2015-05-21  4:11 ` [PATCH 2/6] perf, tools: Allow events with dot Andi Kleen
2015-05-21  4:11 ` [PATCH 3/6] perf, tools: Support CPU id matching for x86 Andi Kleen
2015-05-21  4:11 ` [PATCH 4/6] perf, tools: Support alias descriptions Andi Kleen
2015-05-21  4:11 ` [PATCH 5/6] perf, tools: Query terminal width and use in perf list Andi Kleen
2015-05-21  4:11 ` [PATCH 6/6] perf, tools: Add a --no-desc flag to " Andi Kleen
2015-05-22 15:02 ` perf, tools: Event files for Intel x86 Jiri Olsa
2015-05-22 15:20   ` Andi Kleen
2015-05-22 17:27     ` Jiri Olsa
2015-05-22 16:00   ` Sukadev Bhattiprolu

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=1432181493-18743-1-git-send-email-andi@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=acme@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@kernel.org \
    --cc=sukadev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox