From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Virtualization Mailing List <virtualization@lists.osdl.org>
Subject: Re: Why disable vdso by default with CONFIG_PARAVIRT?
Date: Tue, 12 Dec 2006 04:02:19 +0100 [thread overview]
Message-ID: <200612120402.19958.ak@suse.de> (raw)
In-Reply-To: <457E0460.4030107@goop.org>
On Tuesday 12 December 2006 02:22, Jeremy Fitzhardinge wrote:
> What problem do they cause together? There's certainly no problem with
> Xen+vdso
This was the change which finally got my test system (with an older
SUSE 9.0 based user land to boot). With paravirt older glibc's ld.so
otherwise throws assertation failures because it somehow can't deal with
the new placement. This only happens with paravirt enabled.
Binary compatibility is important.
> (in fact, its actually very useful so that it picks up the
> right libc with Xen-friendly TLS).
AFAIK libc selection comes from the aux vector, not the vdso.
-Andi
next prev parent reply other threads:[~2006-12-12 3:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 1:22 Why disable vdso by default with CONFIG_PARAVIRT? Jeremy Fitzhardinge
2006-12-12 1:42 ` Zachary Amsden
2006-12-12 1:44 ` Jeremy Fitzhardinge
2006-12-12 1:46 ` Zachary Amsden
2006-12-12 1:49 ` Jeremy Fitzhardinge
2006-12-12 3:02 ` Andi Kleen [this message]
2006-12-12 6:28 ` Zachary Amsden
2006-12-12 6:50 ` Jeremy Fitzhardinge
2006-12-12 7:27 ` Andi Kleen
2006-12-12 10:23 ` Jeremy Fitzhardinge
2006-12-12 12:01 ` Andi Kleen
2006-12-12 20:11 ` Jeremy Fitzhardinge
2006-12-12 21:15 ` Andi Kleen
2006-12-13 2:04 ` Rusty Russell
2006-12-13 4:36 ` Rusty Russell
2006-12-13 5:25 ` Rusty Russell
2006-12-12 23:22 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612120402.19958.ak@suse.de \
--to=ak@suse.de \
--cc=jeremy@goop.org \
--cc=virtualization@lists.osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).