WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 2/10] linux 2.6.18: COMPAT_VDSO

To: "Keir Fraser" <keir@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 2/10] linux 2.6.18: COMPAT_VDSO
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Fri, 09 Mar 2007 10:17:33 +0000
Cc: jeremy@xxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 09 Mar 2007 02:17:24 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C211EDE3.A9BC%keir@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <45EC3BE9.76E4.0078.0@xxxxxxxxxx> <C211EDE3.A9BC%keir@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Keir Fraser <keir@xxxxxxxxxxxxx> 05.03.07 16:55 >>>
>On 5/3/07 14:48, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:
>
>> It's gonna be really old libc-s that need an absolutely invariable address.
>> But
>> you certainly recall that in 2.6.16 (and probably earlier) we had a hack to
>> map
>> it in right below PAGE_OFFSET, which worked too for not really new but also
>> not really old libc-s. It is those intermediate libc (supporting AT_SYSINFO
>> but
>> not AT_SYSINFO_EHDR) versions that the option attempts to address for
>> Xen. I happen to have a SuSE 9.0 system still in active use that doesn't work
>> without this option, and I think glibc 2.3.2 shouldn't be considered entirely
>> obsolete, yet.
>
>The build-system approach looks simplest (certainly smaller than the C code)
>but is impenetrable to read. I think we'd take that approach if you add some
>comments to explain what's going on in the makefile runes.

I didn't follow up on this so far because kernel mainline seems to want the fix
for paravirt guests, too, but seems more favorable of the C approach. I haven't
seen anything new on this during the last two days anymore, so would want
to re-inquire whether you wouldn't then change your mind on which approach
to take.

Jan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel