Re: [Xen-devel] Re: [5 Patches] Synchronize blktap with citrix blktap2.

[Dutch Meyer <dmeyer@xxxxxxxxx>]

The build system update I promised is here:
http://www.cs.ubc.ca/~dmeyer/blktap2/userspace_patches.tgz

This removes the blktap2's blktaplib.h from /usr/include so that code with 
blktap dependencies doesn't get confused.
Other patches listed below remain unchanged:
http://www.cs.ubc.ca/~dmeyer/blktap2/kernel_patches.tgz
http://www.cs.ubc.ca/~dmeyer/blktap2/tools_ioemu_dir_use_blktap_old.patch

--Dutch

On Fri, 3 Apr 2009, Dutch Meyer wrote:

> > It seems that the "readonly" flag was removed...but I can't seem to find
> > much documentation, or examples on how this might be used, so I might be
> > way off base here
> Internally, the flag changed to TD_OPEN_RDONLY, but that shouldn't have any 
> effect from a user perspective.  Normal usage shouldn't be changed from the 
> original blktap, you should be able to boot tap disks just as before.
> Internally, the other tap drivers have all been updated to take advantage of 
> the new (and simplified) API.  If you take a look there you'll see the 
> updates.
> > The introduction of the new blktaplib.h does introduce a significant
> > number of new warnings to the qemu build though.
> This is unexpected, but I see now how it could happen under certain 
> conditions.  I will fix this today by NOT installing the "new" blktaplib.h 
> into /usr/include.  This will ensure that anyone who has build anything with 
> #include <blktaplib.h> dependencies will continue to see the old version, 
> which should be appropriate until the old blktap is fully removed.
> --Dutch
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel