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/
Home Products Support Community News


Re: [Xen-devel] [PATCH] blktap: qcow2 image format support

To: Kevin Wolf <kwolf@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] blktap: qcow2 image format support
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 21 Feb 2008 09:20:30 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 21 Feb 2008 01:25:54 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <47BD444A.9080600@xxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ach0awCSPvu38OBeEdy2OAAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] blktap: qcow2 image format support
User-agent: Microsoft-Entourage/
On 21/2/08 09:28, "Kevin Wolf" <kwolf@xxxxxxx> wrote:

> That's a good question. I am not really familiar with the qcow code but
> I think I saw quite some differences. If you put enough effort on it,
> you could probably get a single driver for both, but I can't really
> estimate if it was a sensible thing to do.
> The main reason why I did it this way is that it is the way qemu has
> done it, so I just had to take and adapt their code. I'm not sure if it
> is a good idea to diverge too much from the qemu code base.

Okay that seems reasonable.

 -- Keir

Xen-devel mailing list