From: "Luck, Tony" <tony.luck@intel.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] RE: Fixing /proc/kcore
Date: Mon, 28 Oct 2002 19:03:42 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590709805279@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805249@msgid-missing>
Andi Kleen wrote:
> On Fri, Oct 25, 2002 at 02:14:44PM -0700, Luck, Tony wrote:
> > Putting everything into the vmlist looks to be a good idea. Perhaps
> > there should be an entry for the "direct addresses" too?
>
> Yes that would make sense.
>
> >
> > So what does:
> >
> > # objdump -p /proc/kcore
> >
> > look like for you?
>
> Very messy because of the negative addresses and still some sign problems
> in binutils :-)
Oops, I didn't mean to take this discussion off the mailing list.
What about a combined approach ... architecture dependent code
should add all the interesting stuff to the vmlist, so kcore just
needs to walk the list to cover everything. We could also keep the
KCORE_BASE concept from my patch, but turn it into a variable that
the architecture dependent code can set to some suitable offset to
keep all the offsets in /proc/kcore positive. This will avoid
having to fixup binutils (at least until someone comes up with an
architecture where kernel space scatters across a wide enough range
that we can't keep the offsets positive).
-Tony
next prev parent reply other threads:[~2002-10-28 19:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-25 18:00 [Linux-ia64] Re: Fixing /proc/kcore Andi Kleen
2002-10-28 16:14 ` Mario Smarduch
2002-10-28 19:03 ` Luck, Tony [this message]
2002-10-28 19:10 ` Andi Kleen
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=marc-linux-ia64-105590709805279@msgid-missing \
--to=tony.luck@intel.com \
--cc=linux-ia64@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