From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: acme@kernel.org, jolsa@kernel.org, mingo@kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Support Intel uncore event lists v4
Date: Wed, 11 Jan 2017 19:53:44 +0100 [thread overview]
Message-ID: <20170111185344.GA21289@krava> (raw)
In-Reply-To: <20170110013337.4876-1-andi@firstfloor.org>
On Mon, Jan 09, 2017 at 05:33:26PM -0800, Andi Kleen wrote:
> This adds uncore support on top of the recently merged JSON event list
> infrastructure for core events. Uncore is everything outside the core,
> including memory controllers, PCI, interconnect etc.
>
> Uncore is more complicated to handle than core events because it uses
> many duplicated PMUs, which leads to long event lists and verbose duplicated
> outputs.
>
> In fact previously it was nearly unusable for many cases without special
> tools to generate event list and aggregate data (such as
> https://github.com/andikleen/pmu-tools/tree/master/ucevent)
>
> With this patchkit we add:
> - Basic support for uncore events in JSON events
> - Support aliases that get duplicated over many PMUs transparently
> - Support summing up duplicated PMUs per socket
> - Support extending the perf stat builtin metrics with simple expressions
> specified in the event list.
>
> So far mainly servers are supported. Also this is not using full event lists
> (which are full of very obscure events) but only for a smaller subset of
> curated useful and understandable metrics.
>
> The actual event lists are not posted, but available at
> git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc perf/intel-uncore-json-files-3
>
> The code is available here
> git://git.kernel.org/pub/scm/linux/kernel/git/ak/linux-misc perf/builtin-json-22
>
> v1: Initial post
> v2: Address review feedback. See changelog in commits.
> v3: Repost. Rebase to latest tree.
> v4: Rebase. Change DividedBy to generic simple expression parser.
> Fix refactoring problem that broke git bisect.
> Address review feedback.
>
what's the difference to the post from Jan 03?
jirka
next prev parent reply other threads:[~2017-01-11 18:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 1:33 Support Intel uncore event lists v4 Andi Kleen
2017-01-10 1:33 ` [PATCH 01/11] perf, tools: Factor out scale conversion code Andi Kleen
2017-01-10 1:33 ` [PATCH 02/11] perf, tools: Parse eventcode as number in jevents Andi Kleen
2017-01-10 1:33 ` [PATCH 03/11] perf, tools: Add support for parsing uncore json files Andi Kleen
2017-01-10 1:33 ` [PATCH 04/11] perf, tools: Support per pmu json aliases Andi Kleen
2017-01-10 1:33 ` [PATCH 05/11] perf, tools: Support event aliases for non cpu// pmus Andi Kleen
2017-01-10 1:33 ` [PATCH 06/11] perf, tools: Add debug support for outputing alias string Andi Kleen
2017-01-10 1:33 ` [PATCH 07/11] perf, tools: Collapse identically named events in perf stat Andi Kleen
2017-01-10 1:33 ` [PATCH 08/11] perf, tools: Expand PMU events by prefix match Andi Kleen
2017-01-10 1:33 ` [PATCH 09/11] perf, tools: Add a simple expression parser for JSON Andi Kleen
2017-01-10 1:33 ` [PATCH 10/11] perf, tools: Support MetricExpr header in JSON event list Andi Kleen
2017-01-10 1:33 ` [PATCH 11/11] perf, tools, stat: Output JSON MetricExpr metric Andi Kleen
2017-01-11 18:53 ` Jiri Olsa [this message]
2017-01-11 19:52 ` Support Intel uncore event lists v4 Andi Kleen
2017-01-11 21:47 ` Jiri Olsa
2017-01-11 21:54 ` Andi Kleen
2017-01-12 12:12 ` Jiri Olsa
2017-01-12 17:14 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2017-01-03 15:08 Andi Kleen
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=20170111185344.GA21289@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 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).