From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 vsyscall DSO implementation
Date: 25 Apr 2003 14:00:53 -0700 [thread overview]
Message-ID: <b8c7m5$u3u$1@cesium.transmeta.com> (raw)
In-Reply-To: 16041.24730.267207.671647@napali.hpl.hp.com
Followup to: <16041.24730.267207.671647@napali.hpl.hp.com>
By author: David Mosberger <davidm@napali.hpl.hp.com>
In newsgroup: linux.dev.kernel
>
> I like this. Even better would be if all platforms could do the same.
> I'm definitely interested in doing something similar for ia64 (the
> getunwind() syscall was always just a stop-gap solution).
>
> I assume that these kernel ELF images would then show up in
> dl_iterate_phdr()?
>
> To complete the picture, it would be nice if the kernel ELF images
> were mappable files (either in /sysfs or /proc) and would show up in
> /proc/PID/maps. That way, a distributed application such as a remote
> debugger could gain access to the kernel unwind tables on a remote
> machine (assuming you have a remote filesystem).
>
How about /boot?
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
next prev parent reply other threads:[~2003-04-25 20:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 1:10 [PATCH] i386 vsyscall DSO implementation Roland McGrath
2003-04-25 1:49 ` Jeff Garzik
2003-04-25 2:10 ` Roland McGrath
2003-04-25 16:21 ` David Mosberger
2003-04-25 21:00 ` H. Peter Anvin [this message]
2003-04-25 21:17 ` David Mosberger
2003-04-25 21:20 ` H. Peter Anvin
2003-04-25 21:50 ` David Mosberger
2003-04-26 22:06 ` Roland McGrath
2003-04-26 17:15 ` Ulrich Drepper
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='b8c7m5$u3u$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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;
as well as URLs for NNTP newsgroup(s).