What is the purpose of CONFIG_COMPAT ? It seems to be enabled precisely in 64-bit hypervisors and not otherwise, and is related to support of 32-bit guests including dom0. Is there some reason why this needs to be configurable separately from 64bitness ? Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
>>> Ian Jackson <Ian.Jackson@eu.citrix.com> 07.02.08 14:30 >>> >What is the purpose of CONFIG_COMPAT ? It seems to be enabled >precisely in 64-bit hypervisors and not otherwise, and is related to >support of 32-bit guests including dom0. > >Is there some reason why this needs to be configurable separately from >64bitness ?The original intention was to (a) clearly flag the places that deal with compat mode and (b) permit disabling the feature at build time in case of significant problems. At this point it''s probably no longer necessary to maintain as a separate thing. Jan _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Reasonably Related Threads
- [PATCH v3 09/26] compat_ioctl: move drivers to compat_ptr_ioctl
- [PATCH v3 09/26] compat_ioctl: move drivers to compat_ptr_ioctl
- qemu-xen-traditional: NOCACHE or CACHE_WB to open disk images for IDE
- [PATCH 0/4] Coverity fixes for tools/libxl
- [PATCH RESEND] libxl: Do not generate short block in libxl__datacopier_prefixdata