From: P@draigBrady.com
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: "Hanson, Jonathan M" <jonathan.m.hanson@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: Walking all the physical memory in an x86 system
Date: Tue, 30 Nov 2004 16:01:54 +0000 [thread overview]
Message-ID: <41AC9972.2070305@draigBrady.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0411301654360.20450@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
>> I've written a 2.4 kernel module where I'm trying to walk and
>>record all of the physical memory contents in an x86 system. I have the
>>following code fragment that does it but I suspect I'm missing a portion
>>of the memory:
>>
>>Is there a better way to record all of the contents of physical memory
>>since what I have above doesn't seem to get everything?
>
>
> Maybe something userspace based?
>
> dd_rescue /dev/mem copyofmem
Doesn't equate to a power of 2
(nor does `grep MemTotal /proc/meminfo`)
Pádraig.
next prev parent reply other threads:[~2004-11-30 16:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 15:41 Walking all the physical memory in an x86 system Hanson, Jonathan M
2004-11-30 15:55 ` Jan Engelhardt
2004-11-30 16:01 ` P [this message]
2004-11-30 16:10 ` linux-os
-- strict thread matches above, loose matches on Subject: below --
2004-11-30 16:09 Hanson, Jonathan M
2004-11-30 16:10 ` Jan Engelhardt
2004-11-30 16:12 ` Jan Engelhardt
2004-11-30 17:17 ` Erik Mouw
[not found] ` <41ACADD3.2030206@draigBrady.com>
2004-11-30 17:34 ` Jan Engelhardt
2004-11-30 18:50 ` Alan Cox
2004-11-30 20:25 ` linux-os
2004-11-30 20:46 ` Jan Engelhardt
2004-11-30 20:28 ` Alan Cox
2004-11-30 21:16 Hanson, Jonathan M
2004-11-30 21:26 ` linux-os
2004-11-30 21:28 ` Jan Engelhardt
2004-11-30 21:36 Hanson, Jonathan M
2004-11-30 23:24 Hanson, Jonathan M
2004-12-01 8:37 ` Jan Engelhardt
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=41AC9972.2070305@draigBrady.com \
--to=p@draigbrady.com \
--cc=jengelh@linux01.gwdg.de \
--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.