From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Bharat Bhushan <r65777@freescale.com>,
kvm@vger.kernel.org, bharatb.yadav@gmail.com,
Bharat Bhushan <Bharat.Bhushan@freescale.com>
Subject: Re: [PATCH] KVM:PPC Issue in exit timing clearance
Date: Wed, 23 Mar 2011 11:20:12 +0200 [thread overview]
Message-ID: <4D89BB4C.1060806@redhat.com> (raw)
In-Reply-To: <4D88B1BB.8070306@suse.de>
On 03/22/2011 04:27 PM, Alexander Graf wrote:
>
>>
>> What about using vcpu->requests to have the statistics cleared in
>> vcpu context?
>>
>> What about dropping the whole thing and replacing it with tracepoints?
>
> That should work. The question is if it's worth the effort. The
> current code is there after all :).
>
Tracepoints are wonderful for debugging problems in the field, from my
experience. Removing the special timing code (or rather, moving it to
userspace) is just a bonus.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-03-23 9:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 16:37 [PATCH] KVM:PPC Issue in exit timing clearance Bharat Bhushan
2011-03-22 12:43 ` Avi Kivity
2011-03-22 14:27 ` Alexander Graf
2011-03-23 9:20 ` Avi Kivity [this message]
2011-03-24 2:21 ` Bhushan Bharat-R65777
2011-03-24 10:20 ` Avi Kivity
2011-03-25 4:50 ` Bhushan Bharat-R65777
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=4D89BB4C.1060806@redhat.com \
--to=avi@redhat.com \
--cc=Bharat.Bhushan@freescale.com \
--cc=agraf@suse.de \
--cc=bharatb.yadav@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=r65777@freescale.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