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: David Edmondson <dme@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] Require that xenstored writes to a domain complete in a single chunk
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Mon, 26 Feb 2007 18:14:05 +0000
Delivery-date: Mon, 26 Feb 2007 10:13:28 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <87slcsx11y.fsf@xxxxxxxxxxxxxxxxxxxxxxxxx>
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: AcdZ0eZKJOn1kMXFEdu1UwAX8io7RQ==
Thread-topic: [Xen-devel] Re: [PATCH] Require that xenstored writes to a domain complete in a single chunk
User-agent: Microsoft-Entourage/11.2.5.060620
On 26/2/07 17:48, "David Edmondson" <dme@xxxxxxx> wrote:

>> For older guest compatibility perhaps we can take a variant of your
>> patch that only waits for enough space is the entire message fits in
>> the ring in one go. This would be 'best-effort' at compatibility
>> while not precluding use of larger messages in general.
> 
> Is the implication that you think that this problem could occur with a
> Linux guest (I've never seen it, though have tested much less)?

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.

Oh..... Wait a minute! On Linux we explicitly tear down watches before
suspend. Or at least we used to, before a patch of a few weeks ago (c/s
13519, Jan 19th 2007). This would save us because no watches registered ->
no watches fire. Do you not have anything similar to this in your xenbus
code (presumably you took the dual-licensed files as a basis for the Solaris
implementation)?

So Linux now needs fixing too, but the bug window here has been only a few
weeks and no supported kernel releases include the bug. This being the case
we should probably just fix this issue in current guest kernels.

 -- Keir


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