public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ameya Mitragotri" <ameya.mitragotri@wipro.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Problem with accessing page tables
Date: Tue, 11 Nov 2003 05:14:42 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106852741506159@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106826502101883@msgid-missing>

>   Ameya> Now I think the memory for the swapper_pg_dir has 
> already been
>   Ameya> allocated.
>   Ameya> I still get PMD as 0.
> 
> Again, that's normal for memory that hasn't been allocated yet.
> 
>   Ameya> Am I doing something fundamentally wrong?
> 
> I don't know.  What exactly are you trying to do?

Our assumption is that the addresses for the global variables 
will surely be allocated.
(e.g. &panic_timeout should always resolve to an available PGD,PMD,PTE
and
in the end to a page.)
But we see that it is not happening in our case. (In case of
swapper_pg_dir 
one page is already allocated so it should point to a valid page).
Any valid address which we have taken from System.map does not resolve
down to a 
valid PTE. (??)

The whole purpose of this being, We want to simulate the page tables at
user level
to analyse a crash dump (LKCD) on IA64. So we dump the page tables and
when
Lcrash (the user mode tool for analysing dumps) reads this dump, it can
seek the
page tables and access global variables accordingly. This also will help
us eventually 
in unwinding the dumped stack.

Thanks
Ameya

  parent reply	other threads:[~2003-11-11  5:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-08  4:28 Problem with accessing page tables Ameya Mitragotri
2003-11-08  7:10 ` David Mosberger
2003-11-08  7:58 ` Ameya Mitragotri
2003-11-10 21:45 ` David Mosberger
2003-11-11  5:14 ` Ameya Mitragotri [this message]
2003-11-11  7:33 ` David Mosberger

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-106852741506159@msgid-missing \
    --to=ameya.mitragotri@wipro.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