From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kamala Narasimhan <kamala.narasimhan@gmail.com>
Subject: Re: [PATCH 2/5] Xl interface change plus changes to code
	it impacts
Date: Tue, 08 Feb 2011 13:42:07 -0500
Message-ID: <4D518E7F.3020909@gmail.com>
References: <4D50628A.2000307@gmail.com>	
	<1297175897.9388.114.camel@zakaz.uk.xensource.com>
	<1297176074.9388.116.camel@zakaz.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <1297176074.9388.116.camel@zakaz.uk.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

>> 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.

Kamala