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

[Xen-devel] RE: One question to IST stack for PV guest

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: [Xen-devel] RE: One question to IST stack for PV guest
From: "Kleen, Andi" <andi.kleen@xxxxxxxxx>
Date: Fri, 18 Dec 2009 22:57:06 +0000
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Mon, 21 Dec 2009 08:46:56 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B2C0193.9040407@xxxxxxxx>
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>
References: <C8EDE645B81E5141A8C6B2F73FD9265105AE092F76@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B2BF269.5040608@xxxxxxxx> <2E9E6F5F5978EF44A8590E339E888CF90163515DCF@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B2BF93D.6090807@xxxxxxxx> <2E9E6F5F5978EF44A8590E339E888CF90163515DD2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4B2C0193.9040407@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcqAMSiws1X2Nb5zRSy3AHuiiihn+AAA9PZQ
Thread-topic: One question to IST stack for PV guest
>Are they things a guest domain can do anything useful with? 

Yes they are.

>Or should 
>Xen just handle them internally (and then perhaps tell dom0 about it 
>later if it makes sense)?

When it's corrupted memory and the memory is owned by a particular domain
it has to know about it -- unless you want to kill it outright. But if
you let it know about it can do better than just comitting suicide.
The current mainline kernels don't handle all situations yet, but will
soonish (.34ish hopefully)

-Andi

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