Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for December 5, 2013
Deadline scheduling: coming soon?
LWN.net Weekly Edition for November 27, 2013
ACPI for ARM?
LWN.net Weekly Edition for November 21, 2013
AFAIK the Windows kernel does not support 32-bit entries at all; the compatibility code is completely in userspace.
The hazards of 32/64-bit compatibility
Posted Sep 23, 2010 16:01 UTC (Thu) by nelhage (subscriber, #59579)
The problem of libc having to know about all these random ioctl calls so that it can marshal their parameters between 32-bit and 64-bit mode still exists, though, and I don't see a good solution there.
Posted Sep 23, 2010 16:07 UTC (Thu) by avik (guest, #704)
Posted Sep 23, 2010 17:03 UTC (Thu) by nelhage (subscriber, #59579)
Whereas currently, libc doesn't have to know anything about ioctl formats, it just passes a pointer along. And so if you compile a new kernel module that has some random new ioctl()s, and install the corresponding user programs, everything works. But if libc has to do the marshaling, I also need to update my libc, which is much harder.
Posted Sep 23, 2010 17:35 UTC (Thu) by avik (guest, #704)
(Userspace vs kernel) != (libc vs kernel)
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds