This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Wed, 27 Sep 2006 14:56:32 +0100
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 27 Sep 2006 06:55:26 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <B30DA1341B0CFA4893EF8A36B40B5C5D301A56@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
Thread-index: AcbiF2MEoV3sok4KEdunpAAX8io7RQAGSdMgAADHB8QAAGcR8AAB3oaU
Thread-topic: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XENunstable c/s 11616
User-agent: Microsoft-Entourage/
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", &regs, guest_cpu_user_regs());

This will let us see if the EAX/EDX are garbage on entry to C code
immediately after VMEXIT.

 -- Keir

Xen-devel mailing list