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] Require that xenstored writes to a domain co

To: John Levon <levon@xxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] Require that xenstored writes to a domain complete in a single chunk
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Mon, 26 Feb 2007 23:12:47 +0000
Cc: David Edmondson <dme@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 26 Feb 2007 15:11:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070226190913.GC1983@xxxxxxxxxxxxxxxxxxxxxxx>
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: AcdZ+6Ci310+/sXuEdu1nwAWy6hiGQ==
Thread-topic: [Xen-devel] Re: [PATCH] Require that xenstored writes to a domain complete in a single chunk
User-agent: Microsoft-Entourage/11.3.3.061214
On 26/2/07 19:09, "John Levon" <levon@xxxxxxxxxxxxxxxxx> wrote:

>> The Linux suspend thread does not sync with the xenbus reader thread at all.
>> I'm not sure why we've never seen any problems on Linux, but I guess it's
>> rare that a message cannot be sent all in one go. Especially a watch event,
>> as those are usually fairly short.
> 
> Presumably we have to make sure we've waited for all threads waiting for
> a response to have woken up from the sleep-until-reply too, though; I'm
> not sure we do that.

Request-response pairs are serialised on a mutex. This mutex is locked out
across save/restore, which means that save/restore cannot proceed until any
outstanding response has been fully received. There's nothing even halfway
tricky going on here. :-)

 -- Keir



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