From: Dave Hansen <haveblue@us.ibm.com>
To: "Hanson, Jonathan M" <jonathan.m.hanson@intel.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: Figuring out physical memory regions from a kernel module
Date: Wed, 08 Dec 2004 10:40:27 -0800 [thread overview]
Message-ID: <1102531227.883.4.camel@localhost> (raw)
In-Reply-To: <C863B68032DED14E8EBA9F71EB8FE4C20596020D@azsmsx406>
On Wed, 2004-12-08 at 10:28, Hanson, Jonathan M wrote:
> The module is dumping the contents of physical memory
> and saving the architecture state of the system to a file when triggered
> (ioctl call). What I have works but I need to extend it to systems other
> than my own where I have hard-coded the system RAM regions into the
> code. I need the physical addresses of memory because the tool I feed
> this output into requires this. Here is an example of what the memory
> file looks like:
Sounds like crash dumping. I think they've already run into and
addressed the same general problems.
See crashdump-*.patch in here:
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10-rc2/2.6.10-rc2-mm4/broken-out/
-- Dave
next prev parent reply other threads:[~2004-12-08 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 18:28 Figuring out physical memory regions from a kernel module Hanson, Jonathan M
2004-12-08 18:40 ` Dave Hansen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-08 21:26 Hanson, Jonathan M
2004-12-08 21:38 ` Dave Hansen
2004-12-08 17:54 Hanson, Jonathan M
2004-12-08 17:44 Hanson, Jonathan M
2004-12-08 17:50 ` Arjan van de Ven
2004-12-08 17:57 ` Dave Hansen
2004-12-09 6:25 ` Vivek Goyal
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=1102531227.883.4.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=jonathan.m.hanson@intel.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 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.