linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: davidm@hpl.hp.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 vsyscall DSO implementation
Date: Fri, 25 Apr 2003 14:50:54 -0700	[thread overview]
Message-ID: <16041.44478.599115.696527@napali.hpl.hp.com> (raw)
In-Reply-To: <3EA9A6AF.7060409@zytor.com>

>>>>> On Fri, 25 Apr 2003 14:20:47 -0700, "H. Peter Anvin" <hpa@zytor.com> said:

  hpa> David Mosberger wrote:
  >>  >> 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).

  hpa> How about /boot?
  >>  You mean a regular file?  I'm not sure whether this could be
  >> made to work.  The /proc/PID/maps entry (really: the vm_area for
  >> the kernel ELF images) would have to be created by the kernel, at
  >> a time when no real filesystem is available.  Also, since the
  >> kernel needs to store the data in kernel-memory anyhow, I don't
  >> think there is much point in storing it on disk as well.

  hpa> Perhaps I misunderstood the statement.  With "kernel ELF
  hpa> images" above, I am now gathering you're talking about only the
  hpa> segments exported to userspace (i.e. vsyscall code), not the
  hpa> kernel itself, which was my original reading of that statement.

Sort of.  I used the term "kernel ELF images" to refer to kernel code
that is shared with the user.  I thought that even on x86 this code is
pinned in memory, but perhaps I misunderstood.

Anyhow, it seems to me that using a special filesystem would be more
suitable, as otherwise you get into bootstrap problems etc.

	--david

  reply	other threads:[~2003-04-25 21:38 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
2003-04-25 21:17         ` David Mosberger
2003-04-25 21:20           ` H. Peter Anvin
2003-04-25 21:50             ` David Mosberger [this message]
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=16041.44478.599115.696527@napali.hpl.hp.com \
    --to=davidm@napali.hpl.hp.com \
    --cc=davidm@hpl.hp.com \
    --cc=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).