From: "H. Peter Anvin" <hpa@zytor.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>, Russ Cox <rsc@golang.org>,
Ian Taylor <iant@golang.org>
Subject: Re: vdso feature requests from the Go people
Date: Thu, 12 Jun 2014 22:39:21 -0700 [thread overview]
Message-ID: <539A8E89.5000602@zytor.com> (raw)
In-Reply-To: <CALCETrX9Og2LR3d8HZrcn4uGAgLfxbv51LK4Tsq-gDZKGpsjYw@mail.gmail.com>
On 06/12/2014 10:23 PM, Andy Lutomirski wrote:
>
> As far as I know, there's no reliable way to just read the dynsym
> table -- the thing doesn't have a specified length, which is what
> broke Go in the first place.
>
Ah yes, you're right.
>
> Parsing the ELF dynamic tables is kind of annoyingly complicated, and
> understanding the format is a real PITA -- the documentation I've been
> able to find is outright terrible.
>
Yes... not entirely clear that putting it in the vdso is a net win,
though. There are some people who would like to put a significant chunk
of libc in the vdso, and it just doesn't seem like a good idea.
An index table is somewhat more reasonable, but (a) not backwards
compatible (so wouldn't work with older kernels) and (b) has shades of
Windows...
-hpa
next prev parent reply other threads:[~2014-06-13 5:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-13 4:36 vdso feature requests from the Go people Andy Lutomirski
2014-06-13 4:46 ` Andy Lutomirski
2014-06-13 5:15 ` H. Peter Anvin
2014-06-13 5:23 ` Andy Lutomirski
2014-06-13 5:39 ` H. Peter Anvin [this message]
2014-06-15 9:39 ` Stijn Volckaert
2014-06-13 5:39 ` H. Peter Anvin
2014-06-13 15:34 ` Andy Lutomirski
2014-06-13 16:03 ` H. Peter Anvin
2014-06-15 10:15 ` Stijn Volckaert
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=539A8E89.5000602@zytor.com \
--to=hpa@zytor.com \
--cc=iant@golang.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=rsc@golang.org \
--cc=x86@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