[Xen-devel] Re: "hwcap 0 nosegneg" doesnt work with paravirt_ops

To:	Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject:	[Xen-devel] Re: "hwcap 0 nosegneg" doesnt work with paravirt_ops xen as of 2.6.23.9
From:	Roland McGrath <roland@xxxxxxxxxx>
Date:	Wed, 28 Nov 2007 14:43:59 -0800 (PST)
Cc:	xen-devel@xxxxxxxxxxxxxxxxxxx, Andres Freund <andres@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx
Delivery-date:	Thu, 06 Dec 2007 08:27:47 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	Jeremy Fitzhardinge's message of Wednesday, 28 November 2007 10:12:08 -0800 <474DAF78.8040300@xxxxxxxx>
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:	<200711281829.25532.andres@xxxxxxxxxxx> <474DAF78.8040300@xxxxxxxx>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

> > /etc/ld.so.conf.d/xen.conf:
> > hwcap 0 nosegneg
> 
> This looks OK. [...]

No, it does not match this:

        /* Bit used for the pseudo-hwcap for non-negative segments.  We use
           bit 1 to avoid bugs in some versions of glibc when bit 0 is
           used; the choice is otherwise arbitrary. */
        #define VDSO_NOTE_NONEGSEG_BIT  1

You really want "hwcap 1 nosegneg" given that.
Yes, we've been over this several times already.


Thanks,
Roland

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Re: "hwcap 0 nosegneg" doesnt work with paravirt_ops xen as