From: Keir Fraser <keir@xensource.com>
To: Jan Beulich <jbeulich@novell.com>, Keir Fraser <keir@xensource.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 2/10] linux 2.6.18: COMPAT_VDSO
Date: Mon, 05 Mar 2007 15:55:15 +0000 [thread overview]
Message-ID: <C211EDE3.A9BC%keir@xensource.com> (raw)
In-Reply-To: <45EC3BE9.76E4.0078.0@novell.com>
On 5/3/07 14:48, "Jan Beulich" <jbeulich@novell.com> 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.
-- Keir
next prev parent reply other threads:[~2007-03-05 15:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 11:14 [PATCH 2/10] linux 2.6.18: COMPAT_VDSO Jan Beulich
2007-03-05 13:42 ` Keir Fraser
2007-03-05 14:48 ` Jan Beulich
2007-03-05 15:55 ` Keir Fraser [this message]
2007-03-09 10:17 ` Jan Beulich
2007-03-09 10:39 ` Keir Fraser
2007-03-09 14:59 ` Jeremy Fitzhardinge
2007-03-05 20:07 ` Jeremy Fitzhardinge
2007-03-05 20:07 ` [Xen-devel] " Jeremy Fitzhardinge
2007-03-06 7:52 ` Jan Beulich
2007-03-06 7:52 ` Jan Beulich
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=C211EDE3.A9BC%keir@xensource.com \
--to=keir@xensource.com \
--cc=jbeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.