Re: [xen-devel][PATCH 2/5] Xl interface change plus changes to c

To:	Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Subject:	Re: [xen-devel][PATCH 2/5] Xl interface change plus changes to code it impacts
From:	Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>
Date:	Tue, 08 Feb 2011 13:42:07 -0500
Cc:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Tue, 08 Feb 2011 10:42:45 -0800
Dkim-signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=o/svsZKVCpnPJjhb2CkqeYpOlZQsEUyELdq7pK32iTI=; b=EJWQXcFzp5y1iCHorcY4Juw/93vEnYvk1LzhR+YchpquydWOX/bXTJAvqJ1/D2mMnf 8Fy+b09j/KMmuJqyUgw48JrcP/VmjS7R4VqcVLjU5JHxZ8rFEEWPocV6pCo5Is1ovAYe HXSS7FyjttU7aND4Htux6yDp3ND3T5a8GQzCo=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=e9xVBrsHuLJ3pVyRwsIuWSJ3zpfBh0smylYdhD67KALJ+3QIPUpUkO0DoBuCs0mfpn U/hcJsf1YLyROt0IZsDLrO3Y8pGaIky17oSVAouuvEfZQjnMNlpiGc5X3+WJ656OUBxK wwmQ+pE4j4RjExuNc1wnOSLimcKhdSf1gFWpU=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<1297176074.9388.116.camel@xxxxxxxxxxxxxxxxxxxxxx>
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>
References:	<4D50628A.2000307@xxxxxxxxx> <1297175897.9388.114.camel@xxxxxxxxxxxxxxxxxxxxxx> <1297176074.9388.116.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent:	Thunderbird 2.0.0.24 (X11/20101027)

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


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

WARNING - OLD ARCHIVES

xen-devel

Re: [xen-devel][PATCH 2/5] Xl interface change plus changes to code it i