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][PATCH 2/5] Xl interface change plus changes to code it i

To: Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>
Subject: Re: [xen-devel][PATCH 2/5] Xl interface change plus changes to code it impacts
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Thu, 10 Feb 2011 09:02:28 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 10 Feb 2011 01:03:21 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D518E7F.3020909@xxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <4D50628A.2000307@xxxxxxxxx> <1297175897.9388.114.camel@xxxxxxxxxxxxxxxxxxxxxx> <1297176074.9388.116.camel@xxxxxxxxxxxxxxxxxxxxxx> <4D518E7F.3020909@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2011-02-08 at 18:42 +0000, Kamala Narasimhan wrote:
> >> Did we decide to leave DISK_BACKEND_DEFAULT (i.e. libxl chooses based on
> >> the image type, host's backend support etc) for 4.2? I don't mind if we
> >> did but does that make "block-dev-type" as described in patch 1/5
> >> non-optional? (and therefore not really deprecated)
> > 
> > Maybe this is handled in xl by patch 3/5?
> > 
> > (I should really apply the patch and read the result instead of trying
> > to decode the meaning from the patch form)
> > 
> Yes, a fallback value is set in 3/5 but patch 5/5 will remove that fallback 
> and
> do appropriate validation to better handle this.

Patch 3/5 is all on the xl side though, right? I was meaning a default
"do the right thing" at the libxl interface level, which given time
might become the only option...

I didn't see a patch 5/5 what is in it?

Ian


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