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: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: [PATCH v2 0/7] Remove unused /dev/oldmem interface
Date: Sun, 26 May 2013 14:31:38 +0800 [thread overview]
Message-ID: <51A1AC4A.60506@gmail.com> (raw)
/dev/oldmem provides the interface for us to access the "old memory" in
the dump-capture kernel. Unfortunately, no one actually uses this interface.
And this interface could actually cause some real problems if used on ia64
where the cached/uncached accesses are mixed. See the discussion from
the link: https://lkml.org/lkml/2013/4/12/386.
So Eric suggested that we should remove /dev/oldmem as an unused piece of
code.
Besides, we used a global variable saved_max_pfn to let the capture kernel
know the amount of memory that the previous kernel used. And for almost all
architectures (except x86. In x86, saved_max_pfn is used by detect_calgary()),
the only user of this variable is the read_oldmem interface of /dev/oldmem, so
also remove the setting for saved_max_pfn in those architectures.
-v2:
Keep /dev/oldmem and its number 12 in case this number will get reused in the
future. And mark it obsolete since /dev/oldmem will be removed from kernel.
Zhang Yanfei (7):
/dev/oldmem: Remove this interface
Documentation/devices.txt: Mark /dev/oldmem obsolete
Documentation/kdump/kdump.txt: Remove /dev/oldmem description
mips: Remove savemaxmem parameter setup
powerpc: Remove savemaxmem parameter setup
ia64: Remove setting for saved_max_pfn
s390: Remove setting for saved_max_pfn
Documentation/devices.txt | 3 +-
Documentation/kdump/kdump.txt | 31 +++++--------------------
arch/ia64/kernel/efi.c | 5 ----
arch/mips/kernel/crash_dump.c | 10 --------
arch/powerpc/kernel/crash_dump.c | 10 --------
arch/s390/kernel/setup.c | 4 ---
drivers/char/mem.c | 47 --------------------------------------
7 files changed, 7 insertions(+), 103 deletions(-)
next reply other threads:[~2013-05-26 6:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 6:31 Zhang Yanfei [this message]
2013-05-26 6:34 ` [PATCH v2 1/7] /dev/oldmem: Remove the interface Zhang Yanfei
2013-05-26 6:36 ` [PATCH v2 2/7] Documentation/devices.txt: Mark /dev/oldmem obsolete Zhang Yanfei
2013-05-27 1:46 ` HATAYAMA Daisuke
2013-05-27 1:54 ` Zhang Yanfei
2013-05-27 2:16 ` HATAYAMA Daisuke
2013-05-28 6:17 ` Rob Landley
2013-05-28 6:25 ` Zhang Yanfei
2013-05-28 17:26 ` Rob Landley
2013-05-28 17:35 ` H. Peter Anvin
2013-05-28 22:29 ` Eric W. Biederman
2013-05-29 7:45 ` Zhang Yanfei
2013-05-26 6:38 ` [PATCH v2 3/7] Documentation/kdump/kdump.txt: Remove /dev/oldmem description Zhang Yanfei
2013-05-26 6:40 ` [PATCH v2 4/7] mips: Remove savemaxmem parameter setup Zhang Yanfei
2013-05-26 6:42 ` [PATCH v2 5/7] powerpc: " Zhang Yanfei
2013-05-26 6:44 ` [PATCH v2 6/7] ia64: Remove setting for saved_max_pfn Zhang Yanfei
2013-05-26 6:45 ` [PATCH v2 7/7] s390: " Zhang Yanfei
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=51A1AC4A.60506@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