Xen 
 
Home About Xen.org Xen Xen Summit Wiki Mailing List Bug Tracker Xen Downloads
 
   
 

xen-devel

Re: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/

To: "Li, Xin B" <xin.b.li@xxxxxxxxx>
Subject: Re: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Wed, 27 Sep 2006 19:08:33 +0100
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Steven.Hand@xxxxxxxxxxxx
Delivery-date: Wed, 27 Sep 2006 11:09:00 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: Message from "Li, Xin B" <xin.b.li@xxxxxxxxx> of "Wed, 27 Sep 2006 23:21:06 +0800." <B30DA1341B0CFA4893EF8A36B40B5C5D301A9E@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> >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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel