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] xl: Special case tap/aio for disk validation

To: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] xl: Special case tap/aio for disk validation
From: Kamala Narasimhan <kamala.narasimhan@xxxxxxxxx>
Date: Thu, 27 Jan 2011 12:46:52 -0500
Cc: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>, "Kamala Narasimhan \(3P\)" <kamala.narasimhan@xxxxxxxxxx>
Delivery-date: Thu, 27 Jan 2011 09:51:40 -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=TMZrNzC8tb1/4O4ChAUc5XUlFnW6UYhKiccWa89HaSE=; b=TweFBOQCCsAcZkxpRR95l9UCbU6XCdxiViaWkgj1wlY3WUzyv4Z2OmLpnupG2MxC0f cNfsUYTsVSkozcGL/a3d+mF1DL1sCJKONvSRLXM+Tdb6DkoIL45+4LWaKtKlF0l46XgX WaTsH3/FIT7e+KpSxVFMt4mpxq+u0+mrp6Au4=
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=pTBSygbelWu6pjdshL2/6OVY3guL5CP9M1XDgeyZqj5Xanpu++obgKmSvgkdt+5KcJ L+kZY9UmkO/5N4PRi6aplHdDOLbvCQ6wObZy5BQKrlPgAy1Z70qnl/3OAwCnk4+ncIOD K6LnBwBACI3cjwFwo5z7RVBeHVBFie1k6HxYU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <19777.39923.755279.143976@xxxxxxxxxxxxxxxxxxxxxxxx>
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: <4D407A06.1050902@xxxxxxxxx> <alpine.DEB.2.00.1101271506410.7277@kaball-desktop> <19777.36262.691401.791181@xxxxxxxxxxxxxxxxxxxxxxxx> <1296142527.14780.6892.camel@xxxxxxxxxxxxxxxxxxxxxx> <19777.39923.755279.143976@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.24 (X11/20101027)
>> Shall we pre-deprecate the someprefix: along with all the
>> tap:{aio,ioemu,FOO}: stuff while we are at this? IOW the syntax we want
>> to actually support going forward would be:
>>      (raw|vhd|qcow2|qcow):/path/to/something
>> with the toolstack being at liberty to best decide how to achieve the
>> necessary format support? (optionally raw: as the default). All the rest
>> of the format is really semantically meaningless and supported only for
>> compatibility with existing configuration files.
> 
> Yes.
> 

That brings the question on what we do to make it obvious to the user that we 
are deprecating these options.  That is other than explicitly mentioning it in 
the documentation.  Do we display a warning in our validation code?

Kamala


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