public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhang Yanfei <zhangyanfei.yes@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>,
	Vivek Goyal <vgoyal@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Simon Horman <horms@verge.net.au>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH 3/7] Documentation/kdump/kdump.txt: Remove /dev/oldmem description
Date: Sat, 25 May 2013 11:27:23 +0800	[thread overview]
Message-ID: <51A02F9B.6020904@gmail.com> (raw)
In-Reply-To: <51A02E50.5020507@gmail.com>

From: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>

Signed-off-by: Zhang Yanfei <zhangyanfei@cn.fujitsu.com>
Cc: Vivek Goyal <vgoyal@redhat.com>
---
 Documentation/kdump/kdump.txt |   31 ++++++-------------------------
 1 files changed, 6 insertions(+), 25 deletions(-)

diff --git a/Documentation/kdump/kdump.txt b/Documentation/kdump/kdump.txt
index 9c7fd98..bec123e 100644
--- a/Documentation/kdump/kdump.txt
+++ b/Documentation/kdump/kdump.txt
@@ -47,19 +47,12 @@ parameter. Optionally the size of the ELF header can also be passed
 when using the elfcorehdr=[size[KMG]@]offset[KMG] syntax.
 
 
-With the dump-capture kernel, you can access the memory image, or "old
-memory," in two ways:
-
-- Through a /dev/oldmem device interface. A capture utility can read the
-  device file and write out the memory in raw format. This is a raw dump
-  of memory. Analysis and capture tools must be intelligent enough to
-  determine where to look for the right information.
-
-- Through /proc/vmcore. This exports the dump as an ELF-format file that
-  you can write out using file copy commands such as cp or scp. Further,
-  you can use analysis tools such as the GNU Debugger (GDB) and the Crash
-  tool to debug the dump file. This method ensures that the dump pages are
-  correctly ordered.
+With the dump-capture kernel, you can access the memory image through
+/proc/vmcore. This exports the dump as an ELF-format file that you can
+write out using file copy commands such as cp or scp. Further, you can
+use analysis tools such as the GNU Debugger (GDB) and the Crash tool to
+debug the dump file. This method ensures that the dump pages are correctly
+ordered.
 
 
 Setup and Installation
@@ -423,18 +416,6 @@ the following command:
 
    cp /proc/vmcore <dump-file>
 
-You can also access dumped memory as a /dev/oldmem device for a linear
-and raw view. To create the device, use the following command:
-
-    mknod /dev/oldmem c 1 12
-
-Use the dd command with suitable options for count, bs, and skip to
-access specific portions of the dump.
-
-To see the entire memory, use the following command:
-
-   dd if=/dev/oldmem of=oldmem.001
-
 
 Analysis
 ========
-- 
1.7.1

  parent reply	other threads:[~2013-05-25  3:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25  3:21 [PATCH 0/7] Remove unused /dev/oldmem interface Zhang Yanfei
2013-05-25  3:24 ` [PATCH 1/7] /dev/oldmem: Remove the interface Zhang Yanfei
2013-05-25  3:26 ` [PATCH 2/7] Documentation/devices.txt: Remove /dev/oldmem description Zhang Yanfei
2013-05-25 23:20   ` Eric W. Biederman
2013-05-26  0:58     ` Zhang Yanfei
2013-05-27  1:27       ` HATAYAMA Daisuke
2013-05-27  1:27         ` Zhang Yanfei
2013-05-29 22:20           ` Andrew Morton
2013-05-30  5:49             ` Zhang Yanfei
2013-05-25  3:27 ` Zhang Yanfei [this message]
2013-05-25  3:29 ` [PATCH 4/7] mips: Remove savemaxmem parameter setup Zhang Yanfei
2013-05-25  3:31 ` [PATCH 5/7] powerpc: " Zhang Yanfei
2013-05-25  3:33 ` [PATCH 6/7] ia64: Remove setting for saved_max_pfn Zhang Yanfei
2013-05-25  3:36 ` [PATCH 7/7] s390: " Zhang Yanfei
2013-05-25  7:11 ` [PATCH 0/7] Remove unused /dev/oldmem interface H. Peter Anvin
2013-05-25 23:25 ` Eric W. Biederman
2013-05-28 14:37   ` Vivek Goyal
2013-05-28 15:11     ` H. Peter Anvin
2013-05-29 22:11       ` Andrew Morton
2013-05-28 19:00     ` Eric W. Biederman
2013-05-29 16:10       ` 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=51A02F9B.6020904@gmail.com \
    --to=zhangyanfei.yes@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=horms@verge.net.au \
    --cc=hpa@zytor.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vgoyal@redhat.com \
    /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