search for: xenspecificglibc

...ave you tried doing the same tests > between two different domUs or dom0 and a domU of the same type? > > If you do recompile you could try the Xen TLS glibc patch. > [1] Although I''m not sure if 64bit Xen will work with this. > > [1] http://wiki.xensource.com/xenwiki/XenSpecificGlibc You don''t need a patched glibc for x86_64 Xen as -ve segment offsets aren''t a performance issue. Ian _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...You will understand that this is not very convenient, and will disable more stuff than really needed. Would it possible to add an extra flavor to the current glibc with the correct build options ? Please note that this issue is only available for i386 arch. [1] http://wiki.xensource.com/xenwiki/XenSpecificGlibc Regards, -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type...

Hi, The Gentoo-Wiki about Xen suggests, to add "-mno-tls-direct-seg-refs" to CFLAGS and to recompile the whole system. So it seems, NPTL will work without problems (and without performance drawback) after that. Sweet! But i carefully read http://wiki.xensource.com/xenwiki/XenSpecificGlibc, and it says: "On 32-bit x86 platforms, Xen uses segmentation to provide protection of the memory used for the hypervisor. This results in some performance issues since wrap-around segments as used by glibc need expensive extra handling. For more information on how Xen uses segmentation, see...