From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from [140.186.70.92] (port=52706 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1P5Lxa-00014R-Q5 for qemu-devel@nongnu.org; Mon, 11 Oct 2010 13:14:51 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1P5LxZ-0006BM-Q2 for qemu-devel@nongnu.org; Mon, 11 Oct 2010 13:14:50 -0400 Received: from mail-gy0-f173.google.com ([209.85.160.173]:65108) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1P5LxZ-0006BC-NP for qemu-devel@nongnu.org; Mon, 11 Oct 2010 13:14:49 -0400 Received: by gyb11 with SMTP id 11so191101gyb.4 for ; Mon, 11 Oct 2010 10:14:49 -0700 (PDT) Message-ID: <4CB34605.8030606@codemonkey.ws> Date: Mon, 11 Oct 2010 12:14:45 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH v2 3/7] docs: Add QED image format specification References: <1286552914-27014-1-git-send-email-stefanha@linux.vnet.ibm.com> <1286552914-27014-4-git-send-email-stefanha@linux.vnet.ibm.com> <4CB317EF.7070504@redhat.com> <20101011153039.GD5439@stefan-thinkpad.transitives.com> <4CB32F95.8040301@redhat.com> <20101011154656.GE5439@stefan-thinkpad.transitives.com> <4CB338EC.3080504@codemonkey.ws> In-Reply-To: <4CB338EC.3080504@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi Cc: Kevin Wolf , Christoph Hellwig , Avi Kivity , qemu-devel@nongnu.org On 10/11/2010 11:18 AM, Anthony Liguori wrote: > On 10/11/2010 10:46 AM, Stefan Hajnoczi wrote: >> On Mon, Oct 11, 2010 at 05:39:01PM +0200, Avi Kivity wrote: >>> On 10/11/2010 05:30 PM, Stefan Hajnoczi wrote: >>>>> It was discussed before, but I don't think we came to a >>>>> conclusion. Are >>>>> there any circumstances under which you don't want to set the >>>>> QED_CF_BACKING_FORMAT flag? >>>> I suggest the following: >>>> >>>> QED_CF_BACKING_FORMAT_RAW = 0x1 >>>> >>>> When set, the backing file is a raw image and should not be probed for >>>> its file format. The default (unset) means that the backing image >>>> file >>>> format may be probed. >>>> >>>> Now the backing_fmt_{offset,size} are no longer necessary. >>> Should it not be an incompatible option? If the backing disk starts >>> with a format magic, it will be probed by an older qemu, >>> incorrectly. >> Agreed, it should be a non-compat feature bit. > > If it's just raw or not raw, then I agree it should be non-compat. > > I think we just need a feature bit then that indicates that the > backing file is non-probeable which certainly simplifies the > implementation. > > QED_F_BACKING_FORMAT_NOPROBE maybe? Er, thinking more, this is still a good idea but we still need QED_CF_BACKING_FORMAT because we specifically need to know when a protocol is specified. Otherwise, we have no way of doing nbd as a backing file. Regards, Anthony Liguori > Regards, > > Anthony Liguori > >> Stefan >> >