From: Marcelo Tosatti <mtosatti@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Trace emulated instrucions
Date: Mon, 12 Apr 2010 13:35:23 -0300 [thread overview]
Message-ID: <20100412163523.GA4420@amt.cnet> (raw)
In-Reply-To: <1270980316-20525-1-git-send-email-avi@redhat.com>
On Sun, Apr 11, 2010 at 01:05:14PM +0300, Avi Kivity wrote:
> Add a trace of instruction emulation into ftrace. This can help analyze
> performance issues, or, in the case of failed emulation, identify the
> missing instructions.
>
> v2:
> - trace all emulation starts
> - add missing statistic increment on failure
> (long term we need to get rid of those in favour of perf)
>
> Avi Kivity (2):
> KVM: x86 emulator: Don't overwrite decode cache
> KVM: Trace emulated instructions
>
> arch/x86/kvm/emulate.c | 19 +++++-----
> arch/x86/kvm/trace.h | 86 ++++++++++++++++++++++++++++++++++++++++++++++++
> arch/x86/kvm/x86.c | 4 ++
> 3 files changed, 100 insertions(+), 9 deletions(-)
Applied, thanks.
prev parent reply other threads:[~2010-04-12 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 10:05 [PATCH v2 0/2] Trace emulated instrucions Avi Kivity
2010-04-11 10:05 ` [PATCH 1/2] KVM: x86 emulator: Don't overwrite decode cache Avi Kivity
2010-04-11 10:05 ` [PATCH 2/2] KVM: Trace emulated instructions Avi Kivity
2010-04-12 16:35 ` Marcelo Tosatti [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=20100412163523.GA4420@amt.cnet \
--to=mtosatti@redhat.com \
--cc=avi@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