From: Steven Rostedt <rostedt@goodmis.org>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org, Gleb Natapov <gleb@redhat.com>
Subject: Re: [PATCH] KVM guest: prevent tracing recursion with kvmclock
Date: Tue, 15 Nov 2011 09:01:05 -0500 [thread overview]
Message-ID: <1321365665.4181.11.camel@frodo> (raw)
In-Reply-To: <4EC26CFE.8010406@redhat.com>
On Tue, 2011-11-15 at 15:45 +0200, Avi Kivity wrote:
> What about function traces? Will any noninlined calls cause the same
> problem?
>
Both function_graph and function tracing have recursion protection
around the users of the call. function tracing is much lighter weight
than function_graph tracing. The problem here was that function_graph
tracing does some accounting, and calls the clock handler outside the
recursion protection. I need to add recursion protection around the
accounting too. But I still want to warn when it happens as recursion
protection protects from crashing, but recursion is still bad because it
still goes through a bit of arch specific setup before the recursion is
detected, slowing function_graph tracing down much more than function
tracing when it recurses.
-- Steve
prev parent reply other threads:[~2011-11-15 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 13:01 [PATCH] KVM guest: prevent tracing recursion with kvmclock Avi Kivity
2011-11-15 13:12 ` Gleb Natapov
2011-11-15 13:38 ` Steven Rostedt
2011-11-15 13:45 ` Avi Kivity
2011-11-15 14:01 ` Steven Rostedt [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=1321365665.4181.11.camel@frodo \
--to=rostedt@goodmis.org \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.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