From: David Mosberger <davidm@napali.hpl.hp.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: davidm@hpl.hp.com, Nick Clifton <nickc@redhat.com>,
davidm@napali.hpl.hp.com, gdb@sources.redhat.com,
binutils@sources.redhat.com, roland@redhat.com
Subject: Re: [davidm@napali.hpl.hp.com: readelf question]
Date: Tue, 17 Jun 2003 20:14:00 -0000 [thread overview]
Message-ID: <16111.30389.189801.925393@napali.hpl.hp.com> (raw)
In-Reply-To: <3EEF6B6B.3020308@redhat.com>
>>>>> On Tue, 17 Jun 2003 15:26:35 -0400, Andrew Cagney <ac131313@redhat.com> said:
Andrew> David, I'm guessing that ``gate page'' is vsyscall page?
Yes. To be precise: on ia64, the gate page serves a similar purpose
as on x86 the vsyscall page. (ia64 linux doesn't actually support
virtual syscalls; instead, there are lightweight syscalls, which have
similar performance but aren't restricted to user-mode execution).
Andrew> Whats the Linux kernel status on this one?
They're in the 2.5 tree now (both on x86 and ia64).
Andrew> Last I heard was a kernel patch to make auxv info available
Andrew> in the core file, and via the /proc and ptrace interfaces.
Yes: auxv, core, and ptrace are there. I don't think /proc support is
there. Not sure if Roland is planning to do something about that.
Andrew> Thing is, if that's done, those extra memory sections can go
Andrew> back to being extra memory sections (and everything becomes
Andrew> much simpler).
I don't have much of a preference myself. I'm sure Roland has thought
much more about the user-level parts of the support than I have
(though I do like the idea of being able to get symbol and library
info for the kernel DSO(s); not sure how you'd do that with plain
memory sections).
--david
next prev parent reply other threads:[~2003-06-17 20:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 14:57 H. J. Lu
2003-06-17 8:14 ` Nick Clifton
2003-06-17 18:56 ` David Mosberger
2003-06-17 19:27 ` Andrew Cagney
2003-06-17 20:14 ` David Mosberger [this message]
2003-06-17 20:41 ` Andrew Cagney
2003-06-17 20:44 ` Roland McGrath
2003-06-17 21:00 ` David Mosberger
2003-06-17 21:15 ` Andrew Cagney
2003-06-17 21:06 ` Daniel Jacobowitz
2003-06-17 20:26 ` Roland McGrath
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=16111.30389.189801.925393@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=ac131313@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=davidm@hpl.hp.com \
--cc=gdb@sources.redhat.com \
--cc=nickc@redhat.com \
--cc=roland@redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).