|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/
On 27/9/06 14:09, "Li, Xin B" <xin.b.li@xxxxxxxxx> wrote:
> My log shows that even in the lower 32 bit of eax, there is still some
> garbage value, eax is 0000000000101901, 901 is what we need, but 101 is
> garbage, also edx is garbage, should be all 0.
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", ®s, guest_cpu_user_regs());
show_registers(®s);
}
This will let us see if the EAX/EDX are garbage on entry to C code
immediately after VMEXIT.
-- Keir
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- Re: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616,
Keir Fraser <=
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
- RE: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616, Li, Xin B
|
|
|
|
|