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: [PATCH][HVM] Inject #GP for un-emulated instructions

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] Re: [PATCH][HVM] Inject #GP for un-emulated instructions rather than crash guest
From: "Nakajima, Jun" <jun.nakajima@xxxxxxxxx>
Date: Tue, 27 Nov 2007 09:16:59 -0800
Delivery-date: Tue, 27 Nov 2007 09:18:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3717DE4.10C56%Keir.Fraser@xxxxxxxxxxxx>
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>
References: <FE7BBCFBB500984A9A7922EBC95F516E70F580@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C3717DE4.10C56%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcgwqGajcxL9lyZSSkG/2aFRcODxtwABFqOQAAeF6ycAEujvMA==
Thread-topic: [Xen-devel] Re: [PATCH][HVM] Inject #GP for un-emulated instructions rather than crash guest
Keir Fraser wrote:
> Okay, but would #UD be a better exception to deliver in this case?
Less
> overloaded than #GP and more appropriate?

Since delivering #UD would provide more hints for guests to detect
inconsistency (i.e. incomplete emulation) with instruction handling in
the VM, I think delivering #GP should be more appropriate as a
workaround.

> 
>  -- Keir
> 
> On 27/11/07 04:37, "Cui, Dexuan" <dexuan.cui@xxxxxxxxx> wrote:
> 
> > The CrashMe stress test (a process repeatedly forks child processes,
and
> > the child processes initialize a buffer with random numbers, then
treat
> > the buffer as code, and execute it) can crash 32-bit HVM RHEL5.1
guest
> > easily; this is because we haven't emulated all the instructions in
> > handle_mmio() yet. 
> > 
> > The CrashMe process runs with root rights, and can access MMIO space
in
> > an unknown way ("strace -f" shows the random codes running at CPL=3
> > don't call mmap(), and don't open any special files in /dev/ "); the
gpa
> > may look like 0xa**** or  0xb****, or 0xfee0****.
> > After running CrashMe for several hours, I have found 24 un-emulated
> > instructions may be hit... 
> > 
> > This patch may serve as a workaround.
> > 
> > Signed-off-by: Dexuan Cui <dexuan.cui@xxxxxxxxx>
> > 
> 

Jun
---
Intel Open Source Technology Center

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

<Prev in Thread] Current Thread [Next in Thread>