From: Jiri Olsa <jolsa@redhat.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Namhyung Kim <namhyung@kernel.org>,
Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, acme@redhat.com, namhyung.kim@lge.com
Subject: Re: [PATCH 0/2] perf: add new uncore command
Date: Mon, 4 Feb 2013 14:33:53 +0100 [thread overview]
Message-ID: <20130204133353.GC1058@krava.brq.redhat.com> (raw)
In-Reply-To: <20130202013523.GA2889@tassilo.jf.intel.com>
On Fri, Feb 01, 2013 at 05:35:23PM -0800, Andi Kleen wrote:
> > And there's a patchset [1] from Jiri to support some kind of formula -
> > yeah, now I've written the correct spelling. :) - that might fit to this
> > purpose if you provide suitable formula file IMHO. So I guess we don't
> > need to have another command and can reuse perf stat, no?
>
> Yes with a proper expression engine it's all redundant. I haven't
> looked at Jiri's stuff in detail, but it seemed very simple-minded
> and may not support all the computation needed.
yep, it was just an idea proposal.. it'd need more changes
too be able to handle this uncore stuff, but it's possible
>
> Also would allow to finally replace the bogus perf stat -d frontend/backend
> counters.
yep
>
> For stat there's no really a compelling reason to integrate
> it, the usual wrappers work as well. They have the advantage that
> they can be written in real programing languages, instead of trying
> to invent a new one.
>
> Expressions integrated would be mainly useful for things like
> "counting perf top"
nice idea
jirka
prev parent reply other threads:[~2013-02-04 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 13:54 [PATCH 0/2] perf: add new uncore command Stephane Eranian
2013-01-31 13:54 ` [PATCH 1/2] perf tools: add cpu_map__get_socket() Stephane Eranian
2013-01-31 13:54 ` [PATCH 2/2] perf: add new perf uncore command Stephane Eranian
2013-02-01 8:45 ` Namhyung Kim
2013-01-31 14:21 ` [PATCH 0/2] perf: add new " Ingo Molnar
2013-01-31 14:32 ` Stephane Eranian
2013-02-01 8:42 ` Namhyung Kim
2013-02-02 1:35 ` Andi Kleen
2013-02-04 13:33 ` Jiri Olsa [this message]
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=20130204133353.GC1058@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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