[kvm-devel] [PATCH RFC 1/5]Add some trace enties and define interface for tracing

>From d56731ffc6d5742a88a157dfe0e4344d35f7db58 Mon Sep 17 00:00:00 2001 From: Feng(Eric) Liu <[EMAIL PROTECTED]> Date: Mon, 31 Mar 2008 10:08:55 -0400 Subject: [PATCH] KVM: Add some trace entries in current code and define some interfaces for userspace app to contrl and use tracing data. Signed-of

Re: [kvm-devel] [PATCH RFC 1/5]Add some trace enties and define interface for tracing

Liu, Eric E wrote: > >From d56731ffc6d5742a88a157dfe0e4344d35f7db58 Mon Sep 17 00:00:00 2001 > From: Feng(Eric) Liu <[EMAIL PROTECTED]> > Date: Mon, 31 Mar 2008 10:08:55 -0400 > Subject: [PATCH] KVM: Add some trace entries in current code and define > some interfaces for userspace app to contrl and

Re: [kvm-devel] [PATCH RFC 1/5]Add some trace enties and define interface for tracing

Avi Kivity wrote: > Liu, Eric E wrote: >>> From d56731ffc6d5742a88a157dfe0e4344d35f7db58 Mon Sep 17 00:00:00 >>> 2001 >> From: Feng(Eric) Liu <[EMAIL PROTECTED]> >> Date: Mon, 31 Mar 2008 10:08:55 -0400 >> Subject: [PATCH] KVM: Add some trace entries in current code and >> define some interfaces f

Re: [kvm-devel] [PATCH RFC 1/5]Add some trace enties and define interface for tracing

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.