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] Some question to changeset 17962

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "brendan@xxxxxxxxx" <brendan@xxxxxxxxx>
Subject: RE: [Xen-devel] Some question to changeset 17962
From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
Date: Mon, 9 Mar 2009 17:25:43 +0800
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 09 Mar 2009 02:27:29 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C5DA8493.47DE%keir.fraser@xxxxxxxxxxxxx>
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: <E2263E4A5B2284449EEBD0AAB751098401C7D2A717@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C5DA8493.47DE%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcmgjCFsrvJdjiWJS6eP5QZBhqthpAABW3FXAAHEP9A=
Thread-topic: [Xen-devel] Some question to changeset 17962
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx <> wrote:
> On 09/03/2009 07:53, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> wrote:
> 
>> When I reading changeset 17962, I have several question to it, can anyone
>> give me some hint to it? 
>> 
>> a) The major part of the patch is the affinity for NMI/MCE, what's the
>> relationship between this part with the subject (i.e. the suspend event
>> channel)?
> 
> I incorrectly checked in two patches at once. You should read 17962+17964
> together.

Got it, thanks!

> 
> For (b), Xen itself has okay semantics -- the most recent
> caller to set the
> suspend_evtchn always wins. How tools make use of that policy
> is up to them
> -- since we can only have one save process per domain at a time, it all
> works out fine. 

Are there any special reason that not the first caller hold it (which is more 
nature IMO), and the later caller will failed?

Thanks
-- Yunhong Jiang

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