WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Re: xenpaging fixes for kernel and hypervisor

To: Patrick Colp <pjcolp@xxxxxxxxx>, Olaf Hering <olaf@xxxxxxxxx>
Subject: Re: [Xen-devel] Re: xenpaging fixes for kernel and hypervisor
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 22 Sep 2010 18:13:33 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 22 Sep 2010 10:14:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AANLkTinYe8T+Fwt97ajsEKPUNhCOvBP+WxprseKd17RA@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: ActadjIGbF+ut0b7RtGIr5VbyV+7hQAA0oXr
Thread-topic: [Xen-devel] Re: xenpaging fixes for kernel and hypervisor
User-agent: Microsoft-Entourage/12.26.0.100708
On 22/09/2010 17:49, "Patrick Colp" <pjcolp@xxxxxxxxx> wrote:

> I don't know if I need to ack or not, but I will:
> 
> Acked-by: Patrick Colp <pjcolp@xxxxxxxxx>
> 
> 
> I think the issue with realmode is in the emulation code. Looking at
> where that crash occurs, it's a result of hvm_emulate_one() returning
> X86EMUL_UNHANDLEABLE. hvm_emulate_one() calls x86_emulate(), and for
> supported functions, that will call hvmemul_* using the
> hvm_emulate_ops pointer function struct. However, my guess is that
> what's causing this problem is an instruction that isn't handled by
> that stuff (the hvmemul_* stuff).

The instruction is dumped as "0f 00 00 00 00 ..." which is a bit unlikely to
be a real instruction. Something went wrong before that point, most likely.

 -- Keir



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