From: Andi Kleen <ak@linux.intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, acme@redhat.com, jolsa@redhat.com,
namhyung.kim@lge.com
Subject: Re: [PATCH 0/2] perf: add new uncore command
Date: Fri, 1 Feb 2013 17:35:23 -0800 [thread overview]
Message-ID: <20130202013523.GA2889@tassilo.jf.intel.com> (raw)
In-Reply-To: <878v78togq.fsf@sejong.aot.lge.com>
> 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.
Also would allow to finally replace the bogus perf stat -d frontend/backend
counters.
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"
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2013-02-02 1:35 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 [this message]
2013-02-04 13:33 ` 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=20130202013523.GA2889@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.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 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.