Xen devel - Sep 2006 - RE: Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616

>Since this happens early in HVM guest boot, I suggest adding tracing
to
>vmx_vmexit_handler() to dump registers on every MSR write. 
>Something like
>this early on in the function:
> if ( reason == EXIT_REASON_MSR_WRITE ) {
>     printk("regs==%p, guest_regs==%p\n", &regs, 
>guest_cpu_user_regs());
>     show_registers(&regs);
> }
>
>This will let us see if the EAX/EDX are garbage on entry to C code
>immediately after VMEXIT.
This patch doesn''t help, after applying it, all is OK.
-Xin

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

> >Since this happens early in HVM guest boot, I suggest adding tracing
>to
>>vmx_vmexit_handler() to dump registers on every MSR write.=20
>>Something like
>>this early on in the function:
>> if ( reason =3D=3D EXIT_REASON_MSR_WRITE ) {
>>     printk("regs=3D=3D%p, guest_regs=3D=3D%p\n",
&regs,=20
>>guest_cpu_user_regs());
>>     show_registers(&regs);
>> }
>>
>>This will let us see if the EAX/EDX are garbage on entry to C code
>>immediately after VMEXIT.
>
>This patch doesn''t help, after applying it, all is OK.
Hmm.

So this seems to be a compiler/linker issue - any chance you can post 
a URL for the xen-syms for a ''broken'' case? 

(i.e. a non-debug build built using gcc 4.0.0 or 4.1.0 or similar)


cheers,

S.



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel