From: Jim Houston <jim.houston@comcast.net>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: x86_64 vdso patch status?
Date: Mon, 26 Feb 2007 13:33:49 -0500 [thread overview]
Message-ID: <1172514829.7749.17.camel@x2.site> (raw)
Hi Andi,
I tried playing with your vdso patch. I'm curious
what magic is needed to make an application link with
the vdso?
You also mentioned that there are problems with newer
tool chains. I think I'm seeing this problem when I
build on an FC6 system. The vdso.so ends up using
file offsets like 00100120 so it doesn't fit in a
single page. This seems to be sensitive to the
VDSO_PRELINK address. If I changes this address to
0xffffffffff800000 then the vdso.so looks correct.
Is this change safe? Is it enough to change the
VDSO_PRELINK define or are there other values which
need to be kept in sync?
Jim Houston - Concurrent Computer Corp.
reply other threads:[~2007-02-26 18:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1172514829.7749.17.camel@x2.site \
--to=jim.houston@comcast.net \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®