Re: [Xen-devel] [PATCH 0 of 7] libxl: refactor tap disk handling

[Christoph Egger <Christoph.Egger@xxxxxxx>]

On 04/07/11 11:52, Ian Campbell wrote:
> I'm not personally convinced that support for blktap2 devices should
> be conflated in libxl with the PV block backend support but given it's
> there lets at least correct it.
>
> In a blktap2 system there is no "tap" PV backend type. blktap2 exposes
> a standard block device and this is passed to a guest using the
> standard blkback "vbd" (sometimes called "phy") backend. Drop the
> "tap" backend type and associated (libxl internal ) DEVICE_TAP
> enumeration value.
What happens on a no-blktap2 system?

> Also try and clarify the paths which fallback from blktap2 to qdisk
> when the former is not present. Falling through a switch statement is
> a neat way of doing this in some cases, but I don't think this is one
> of them.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632


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