From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Kevin Wolf <kwolf@suse.de>
Subject: Re: [PATCH] blktap: qcow2 image format support
Date: Thu, 21 Feb 2008 10:07:14 +0100 [thread overview]
Message-ID: <200802211007.14443.Christoph.Egger@amd.com> (raw)
In-Reply-To: <C3E2ED8C.1430F%Keir.Fraser@cl.cam.ac.uk>
On Thursday 21 February 2008 09:57:48 Keir Fraser wrote:
> On 21/2/08 08:49, "Kevin Wolf" <kwolf@suse.de> wrote:
> > This patch adds support for the qcow2 image format to blktap. It
> > consists mostly of qemu code, adapted to the blktap interfaces.
> > Snapshots and compressed images are supported.
> >
> > The qcow2 driver may be used by either specifying tap:qcow2 or by using
> > tap:qcow which will detect that you have a version 2 image and will call
> > the qcow2 driver.
>
> Is qcow2 so different from qcow1 that it really needs its own backend
> driver?
IMO, _all_ blktap drivers need some code refactoring. There is a lot of
duplicated code across all drivers
that can be moved into a blktap/drivers/blk-common.c.
Christoph
--
AMD Saxony, Dresden, Germany
Operating System Research Center
Legal Information:
AMD Saxony Limited Liability Company & Co. KG
Sitz (Geschäftsanschrift):
Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland
Registergericht Dresden: HRA 4896
vertretungsberechtigter Komplementär:
AMD Saxony LLC (Sitz Wilmington, Delaware, USA)
Geschäftsführer der AMD Saxony LLC:
Dr. Hans-R. Deppe, Thomas McCoy
next prev parent reply other threads:[~2008-02-21 9:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 8:49 [PATCH] blktap: qcow2 image format support Kevin Wolf
2008-02-21 8:57 ` Keir Fraser
2008-02-21 9:07 ` Christoph Egger [this message]
2008-02-21 9:32 ` Kevin Wolf
2008-02-21 12:47 ` Daniel P. Berrange
2008-02-21 17:18 ` Ian Jackson
2008-02-21 9:28 ` Kevin Wolf
2008-02-21 9:20 ` Keir Fraser
2008-02-21 10:31 ` Keir Fraser
2008-02-24 3:12 ` Kurt Hackel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200802211007.14443.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=kwolf@suse.de \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.