From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
"ak@linux.intel.com" <ak@linux.intel.com>,
Jiri Olsa <jolsa@redhat.com>,
"Yan, Zheng" <zheng.z.yan@intel.com>
Subject: Re: [PATCH v2 0/3] perf,x86: add Intel RAPL PMU support
Date: Wed, 23 Oct 2013 12:22:52 -0200 [thread overview]
Message-ID: <20131023142251.GA4034@infradead.org> (raw)
In-Reply-To: <CABPqkBSSFFVHH657-bvis4sSz9av4V4ziG4TVdmMZhO4LMfAdw@mail.gmail.com>
Em Wed, Oct 23, 2013 at 11:34:42AM +0200, Stephane Eranian escreveu:
> On Wed, Oct 23, 2013 at 12:18 AM, Arnaldo Carvalho de Melo
> > What about:
> > # perf stat -a -e power/energy-cores/,power/energy-pkg/,ref-cycles -I 1000 sleep 1000
> > # time events
> > 1.000264953 2.09 Joules power/energy-cores/
> > 1.000264953 5.94 Joules power/energy-pkg/
> > 1.000264953 160,530,320 ref-cycles
> > 2.000640422 2.07 Joules power/energy-cores/
> > 2.000640422 5.94 Joules power/energy-pkg/
> > 2.000640422 152,673,056 ref-cycles
> > 3.000964416 2.08 Joules power/energy-cores/
> > 3.000964416 5.93 Joules power/energy-pkg/
> > 3.000964416 158,779,184 ref-cycles
> > ?
> > Or even 2.09J power/energy-cores/?
> I can try that.
> > I.e. a perf_evsel__fprintf_value(evsel) would append a unit string, if
> > available.
> I don't have this function is my tree yet (tip.git).
That would be a new one :-)
At some point I'll study the %pM, etc things in the kernel printk code
to come up with something like perf_evsel__{f,scn}printf that allows us
to use just one string format and then pick things like units as a
modifier, but till then having these fprintf variants seems good enough.
- Arnaldo
next prev parent reply other threads:[~2013-10-23 14:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-10 14:50 [PATCH v2 0/3] perf,x86: add Intel RAPL PMU support Stephane Eranian
2013-10-10 14:50 ` [PATCH v2 1/3] perf: add active_entry list head to struct perf_event Stephane Eranian
2013-10-10 14:50 ` [PATCH v2 2/3] perf,x86: add Intel RAPL PMU support Stephane Eranian
2013-10-10 14:50 ` [PATCH v2 3/3] perf,x86: add RAPL hrtimer support Stephane Eranian
2013-10-10 17:43 ` [PATCH v2 0/3] perf,x86: add Intel RAPL PMU support Andi Kleen
2013-10-10 18:00 ` Borislav Petkov
2013-10-16 12:46 ` Ingo Molnar
2013-10-16 13:13 ` Stephane Eranian
2013-10-16 17:53 ` Arnaldo Carvalho de Melo
2013-10-16 18:14 ` Stephane Eranian
2013-10-17 8:14 ` Ingo Molnar
2013-10-17 9:07 ` Peter Zijlstra
2013-10-17 9:12 ` Borislav Petkov
2013-10-17 20:09 ` Stephane Eranian
2013-10-22 16:47 ` Stephane Eranian
2013-10-22 22:18 ` Arnaldo Carvalho de Melo
2013-10-23 9:34 ` Stephane Eranian
2013-10-23 14:22 ` Arnaldo Carvalho de Melo [this message]
2013-10-23 14:33 ` Stephane Eranian
2013-10-23 7:07 ` Andi Kleen
2013-10-23 9:24 ` Stephane Eranian
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=20131023142251.GA4034@infradead.org \
--to=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=zheng.z.yan@intel.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