From: Avi Kivity <avi@qumranet.com>
To: "Liu, Eric E" <eric.e.liu@intel.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>
Subject: Re: [PATCH RFC 1/5]Add some trace enties and define interface for tracing
Date: Wed, 09 Apr 2008 00:53:25 +0300 [thread overview]
Message-ID: <47FBE955.7090709@qumranet.com> (raw)
In-Reply-To: <9D7649D18729DE4BB2BD7B494F7FEDC2011FC89E@pdsmsx415.ccr.corp.intel.com>
Liu, Eric E wrote:
>>
>> High order 32 bits of cr2 are lost.
>>
>>
>
> May I use KVMTRACE_3D(PAGE_FAULT, vcpu, error_code, (u32)cr2,
> (u32)((u64)cr2 >> 32), handler) to handle this?
> for 32bit gust, it traces some excess data, but after all for 64bit
> guest, we don't lost high order bits.
>
>
Sure.
>
>
>>> }
>>> -
>>> + KVMTRACE_1D(INJ_VIRQ, vcpu, idtv_info_field, handler);
>>>
>>>
>> Probably need a different marker than INJ_VIRQ, as this is on exit,
>> not entry.
>>
>>
>
> Is the marker REDELIVER_EVT ok for this?
>
>
Yes.
>>> @@ -2428,6 +2445,7 @@ void kvm_arch_exit(void)
>>> int kvm_emulate_halt(struct kvm_vcpu *vcpu)
>>> {
>>> ++vcpu->stat.halt_exits;
>>> + KVMTRACE_0D(HLT, vcpu, handler);
>>> if (irqchip_in_kernel(vcpu->kvm)) {
>>> vcpu->arch.mp_state = VCPU_MP_STATE_HALTED;
>>> kvm_vcpu_block(vcpu);
>>>
>>>
>> Would be nice to have an UNHLT to see how long sleeps are. But this
>> will probably be seen by the irq injection.
>>
>
> I think from the cycles Between VMEXIT( caused by halt) and VMENTRY we
> can evaluate how long sleeps are.
>
Right.
We'll merge it with the understanding that the data format is not part
of the ABI and will change between versions. It will cause some
headaches when people send us traces, but on the other hand will give us
some flexibility.
--
Any sufficiently difficult bug is indistinguishable from a feature.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Register now and save $200. Hurry, offer ends at 11:59 p.m.,
Monday, April 7! Use priority code J8TLD2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
prev parent reply other threads:[~2008-04-08 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 6:18 [PATCH RFC 1/5]Add some trace enties and define interface for tracing Liu, Eric E
2008-04-03 10:50 ` Avi Kivity
2008-04-08 3:34 ` Liu, Eric E
2008-04-08 21:53 ` Avi Kivity [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=47FBE955.7090709@qumranet.com \
--to=avi@qumranet.com \
--cc=eric.e.liu@intel.com \
--cc=kvm-devel@lists.sourceforge.net \
/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