From: Karim Yaghmour <karim.yaghmour@opersys.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
mingo@elte.hu
Subject: Re: Reading perf counters at ftrace trace boundaries
Date: Sun, 11 Aug 2013 22:39:00 -0300 [thread overview]
Message-ID: <52083CB4.2030308@opersys.com> (raw)
In-Reply-To: <87haevog75.fsf@tassilo.jf.intel.com>
On 13-08-11 10:23 PM, Andi Kleen wrote:
> KVM does it, see arch/x86/kvm/pmu.c. Essentially it would be doing RDPMC.
Thx for the pointer, appreciated.
> But the overhead will be likely very high, some sampling approach
> is likely better.
Indeed. It doesn't actually have to be at every single ftrace
begin/exit. But possibly starting with some kind of every nth and then
drilling down as the culprit is incrementally singled-out.
--
Karim Yaghmour
CEO - Opersys inc. / www.opersys.com
http://twitter.com/karimyaghmour
next prev parent reply other threads:[~2013-08-12 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-12 0:03 Reading perf counters at ftrace trace boundaries Karim Yaghmour
2013-08-12 1:23 ` Andi Kleen
2013-08-12 1:39 ` Karim Yaghmour [this message]
2013-08-12 1:47 ` Andi Kleen
2013-08-12 1:59 ` Karim Yaghmour
2013-08-12 2:24 ` zhangwei(Jovi)
2013-08-12 15:26 ` Karim Yaghmour
2013-08-13 7:12 ` zhangwei(Jovi)
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=52083CB4.2030308@opersys.com \
--to=karim.yaghmour@opersys.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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