|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Information required on TRACE_VMEXIT working.
On 11/27/06, aditya shevalkar <aditya27783@xxxxxxxxxxx> wrote:
I think the missing piece of the puzzle are the following functions,
also found in vmx.c:
asmlinkage void vmx_trace_vmentry(void)
{
struct vcpu *v = current;
TRACE_5D(TRC_VMX_VMENTRY + current->vcpu_id,
v->arch.hvm_vcpu.hvm_trace_values[0],
v->arch.hvm_vcpu.hvm_trace_values[1],
v->arch.hvm_vcpu.hvm_trace_values[2],
v->arch.hvm_vcpu.hvm_trace_values[3],
v->arch.hvm_vcpu.hvm_trace_values[4]);
TRACE_VMEXIT(0, 0);
TRACE_VMEXIT(1, 0);
TRACE_VMEXIT(2, 0);
TRACE_VMEXIT(3, 0);
TRACE_VMEXIT(4, 0);
}
asmlinkage void vmx_trace_vmexit (void)
{
TRACE_3D(TRC_VMX_VMEXIT + current->vcpu_id, 0, 0, 0);
}
When a VMEXIT happens, vmx_trace_vmexit() is called, and a trace
record is generated. (This includes an RDTSC timetamp). Then, as the
VMEXIT is handled, the various trace_values[] are filled in, depending
upon what kind of vmexit it is. Then, just before the next
With Regards, Aditya Shevalkar. __________________________________________________________ Yahoo! India Answers: Share what you know. Learn something new http://in.answers.yahoo.com/ _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |