Chris Lalancette
2008-Jul-09 00:26 UTC
[Xen-devel] [PATCH 1/3]: Blktapctrl compatibility layer
I originally had just changed the NEWINTF ioctl to send over 48-bits of information, which works on 64-bit but not on 32-bit (since the arg is an unsigned long). Additionally, the previous changes would break an older userland against a new kernel. For that reason, introduce a new ioctl (NEWINTF_EXT) that fixes both of these problems. This is the dom0 userland side. Signed-off-by: Chris Lalancette <clalance@redhat.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ryan O''Connor
2008-Jul-09 17:31 UTC
Re: [Xen-devel] [PATCH 1/3]: Blktapctrl compatibility layer
On Wed, Jul 09, 2008 at 02:26:01AM +0200, Chris Lalancette wrote:> I originally had just changed the NEWINTF ioctl to send over 48-bits of > information, which works on 64-bit but not on 32-bit (since the arg is an > unsigned long). Additionally, the previous changes would break an older > userland against a new kernel. For that reason, introduce a new ioctl > (NEWINTF_EXT) that fixes both of these problems. This is the dom0 userland side. > > Signed-off-by: Chris Lalancette <clalance@redhat.com> >I tested this lats night, and I see that it''s been committed. I can confirm that it resolves the issue reported by Chris Head. thanks, R -- Ryan O''Connor <rjo@cs.ubc.ca> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Chris Lalancette
2008-Jul-09 17:49 UTC
Re: [Xen-devel] [PATCH 1/3]: Blktapctrl compatibility layer
Ryan O''Connor wrote:> I tested this lats night, and I see that it''s been committed. I can > confirm that it resolves the issue reported by Chris Head.Excellent, thanks for the testing. Chris Lalancette _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel