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/
Home Products Support Community News


[Xen-devel] Re: [PATCH] Block device bringup using Xenstore

To: Mike Wray <mike.wray@xxxxxx>
Subject: [Xen-devel] Re: [PATCH] Block device bringup using Xenstore
From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Date: Fri, 08 Jul 2005 04:27:51 +1000
Cc: Xen Mailing List <xen-devel@xxxxxxxxxxxxxxxxxxx>, Christian Limpach <Christian.Limpach@xxxxxxxxxxxx>
Delivery-date: Thu, 07 Jul 2005 18:26:38 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <42CD07D2.6080001@xxxxxx>
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: <1120723536.12218.37.camel@xxxxxxxxxxxxxxxxxxxxx> <42CD07D2.6080001@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Thu, 2005-07-07 at 11:45 +0100, Mike Wray wrote:
> Rusty Russell wrote:
> > This megapatch updates the xenstore daemon, updates the xenbus code, and
> > hacks the block devices to use the store rather than control messages
> > for initialization.

> Block device and network interface setup has been working in the control
> tools CVS for several days, and is fully integrated with the xend tools.
> It would be more helpful if you would integrate with that code instead
> of going off on your own.

No.  I completely disagree with what you've done.  I disagree with how
you use the store, both here and in most other places.  Your changes
made the xenbus code more complicated to suit a usage model which is a
retrograde step.

Rather than criticise in the abstract, I believe that the way to solve
these kind of disputes is to present a concrete implementation of one's
idea, so people can compare.  I don't expect you to implement my vision
of how things should be, but it's completely incompatible with your
work, and I've finally had the opportunity to implement it.

I will continue to develop this as my conscience dictates.  You should
do the same.  As always, I aim to create code which is convincing in

A bad analogy is like a leaky screwdriver -- Richard Braakman

Xen-devel mailing list