From: Russell King <rmk@arm.linux.org.uk>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: /proc/kcore - how to fix it
Date: Sat, 24 May 2003 07:38:07 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723706028@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705961@msgid-missing>
On Fri, May 23, 2003 at 04:51:43PM -0700, Luck, Tony wrote:
> > One alternative I considered was to use just do a page table lookup.
> > But I fear that some architectures use direct mapping registers etc.
> > with mappings not in the page tables for the direct mapping, so it
> > probably won't work for everybody.
>
> You are right. IA64 maps the kernel with some locked registers, so
> there are no pagetables to show that the mapping exists.
ARM maps the kernel direct-mapped RAM using 1MB section mappings, which
the normal pgd/pmd/pte macros don't recognise as being valid.
> I don't know ... you'll have to dust off those fixes for /proc to let
> the negative file offsets get as far as the kcore.c code so we can
> see what utilities work. In practice we probably don't care about
> anything other than gdb.
gdb definitely breaks - that's why I had to do the changes in the first
place. gdb tries to lseek to negative 64-bit file offsets, which the
kernel rejects with EINVAL iirc. (Tried it earlier this week.)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
prev parent reply other threads:[~2003-05-24 7:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 20:30 [Linux-ia64] Re: /proc/kcore - how to fix it Valdis.Kletnieks
2003-05-23 19:13 ` [Linux-ia64] " Luck, Tony
2003-05-23 19:41 ` [Linux-ia64] " Andi Kleen
2003-05-23 20:52 ` [Linux-ia64] " Luck, Tony
2003-05-23 21:11 ` [Linux-ia64] " Russell King
2003-05-23 21:39 ` Andi Kleen
2003-05-23 23:43 ` [Linux-ia64] " Luck, Tony
2003-05-23 23:51 ` Luck, Tony
2003-05-24 7:38 ` Russell King [this message]
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-105590723706028@msgid-missing \
--to=rmk@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.