From: Andi Kleen <andi@firstfloor.org>
To: Aaron Lindsay <alindsay@codeaurora.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Digant Desai <digantd@codeaurora.org>,
timur@codeaurora.org
Subject: Re: [PATCH] perf stat: Add event-interval-print option
Date: Thu, 24 Aug 2017 13:51:59 -0700 [thread overview]
Message-ID: <20170824205158.GM2482@two.firstfloor.org> (raw)
In-Reply-To: <20170824203902.GA5620@codeaurora.org>
On Thu, Aug 24, 2017 at 04:39:02PM -0400, Aaron Lindsay wrote:
> Does anyone have any feedback on this patch or the idea in general?
>
> Also, (for our bookkeeping - not trying to rush things) is there any
> chance this will still make it in for the 4.14 merge window, or is it
> 4.15 material at the earliest?
You can already do that with leader sampling through perf record
e.g.
% perf record -e '{cpu/cpu-cycles,period=10000/,branches,branch-misses}:S' ...
% perf script
swapper 0 [005] 3905226.804037: 10210 cpu/cpu-cycles,period=10000/: ffffffff9e87643c intel_idle ([kernel.kallsyms])
swapper 0 [005] 3905226.804037: 345 branches: ffffffff9e87643c intel_idle ([kernel.kallsyms])
swapper 0 [005] 3905226.804037: 58 branch-misses: ffffffff9e87643c intel_idle ([kernel.kallsyms])
:16797 16797 [004] 3905226.804038: 10160 cpu/cpu-cycles,period=10000/: ffffffffc07fdd10 kvm_fetch_guest_virt ([kvm])
:16797 16797 [004] 3905226.804038: 515 branches: ffffffffc07fdd10 kvm_fetch_guest_virt ([kvm])
:16797 16797 [004] 3905226.804038: 19 branch-misses: ffffffffc07fdd10 kvm_fetch_guest_virt ([kvm])
Yes it's a useful technique.
-Andi
prev parent reply other threads:[~2017-08-24 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-16 15:08 [PATCH] perf stat: Add event-interval-print option Aaron Lindsay
2017-08-24 20:39 ` Aaron Lindsay
2017-08-24 20:51 ` Andi Kleen [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=20170824205158.GM2482@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alindsay@codeaurora.org \
--cc=digantd@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=timur@codeaurora.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.