From: Simon Horman <horms@verge.net.au>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: "kexec@lists.infradead.org" <kexec@lists.infradead.org>,
Zhang Yanfei <zhangyanfei.yes@gmail.com>
Subject: Re: [PATCH 0/4] kexec-tools: Remove saved_max_mem
Date: Mon, 10 Jun 2013 17:35:51 +0900 [thread overview]
Message-ID: <20130610083551.GC1563@verge.net.au> (raw)
In-Reply-To: <87obbu7mxg.fsf@xmission.com>
On Tue, May 28, 2013 at 03:35:23PM -0700, Eric W. Biederman wrote:
> Zhang Yanfei <zhangyanfei.yes@gmail.com> writes:
>
> > When loading the dump-capture kernel, in some architectures(mips/ppc/ppc64),
> > we should add the parameter "savemaxmem=" in the dump-capture kernel
> > commandline to tell the new kernel the amount of memory that the previous
> > kernel used.
> >
> > Then in the dump-capture kernel, we parse this parameter and assign the
> > value to saved_max_pfn. In these architectures, the only user of
> > saved_max_pfn is the read interface read_oldmem for /dev/oldmem.
> >
> > But, no one actually uses the /dev/oldmem interface. And we have decided
> > to remove the /dev/oldmem interface. A kernel side patch to remove this
> > interface have been sent. See https://lkml.org/lkml/2013/5/24/451.
> >
> > So in kexec-tools, we don't need to pass this parameter anymore. This
> > patchset aims to remove the related variables and funtions in
> > kexec-tools.
>
> To this series.
>
> Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
>
> No one cares unless they are actually using /dev/oldmem, and so far
> it appears no one actually uses /dev/oldmem so this change looks very
> safe.
Thanks, all four patches applied.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2013-06-10 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-26 3:38 [PATCH 0/4] kexec-tools: Remove saved_max_mem Zhang Yanfei
2013-05-26 3:40 ` [PATCH 1/4] kexec-tools: mips: " Zhang Yanfei
2013-05-26 3:40 ` [PATCH 2/4] kexec-tools: ppc: " Zhang Yanfei
2013-05-26 3:41 ` [PATCH 3/4] kexec-tools: ppc64: " Zhang Yanfei
2013-05-26 3:41 ` [PATCH 4/4] kexec-tools: sh: " Zhang Yanfei
2013-05-28 22:35 ` [PATCH 0/4] kexec-tools: " Eric W. Biederman
2013-06-10 8:35 ` Simon Horman [this message]
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=20130610083551.GC1563@verge.net.au \
--to=horms@verge.net.au \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=zhangyanfei.yes@gmail.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