From: Michael Neuling <mikey@neuling•org>
To: mohan@in•ibm.com
Cc: fastboot@osdl•org, linuxppc-dev@ozlabs•org
Subject: Re: [Fastboot] [PATCH] Reserve crashkernel memory region
Date: Fri, 28 Apr 2006 17:06:26 +1000 [thread overview]
Message-ID: <20060428070704.4AD0A679F5@ozlabs.org> (raw)
In-Reply-To: <20060424061015.GA31320@in.ibm.com>
> Now kexec'ed kernel in a PPC64 machine does not reserve memory for
> crashkernel region. So kexec'ed kernel can not load kdump kernel
> reliably.
Owww 3 boots... scary :-)
> Attached kexec-tools patch reserves memory for kdump kernel by adding
> an entry in the reserve memory table. So while kexec'ed kernel is
> booting, it reserves memory for crashkernel region.
This logic is duplicated in prom_init.c.
It'd be cool if the kernel parsed the command line early on (after
prom_init.c) and did the memory reserves there. Then we wouldn't need
this logic in both the kexec tools and prom_init.c.
Mikey
prev parent reply other threads:[~2006-04-28 7:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 6:10 [PATCH] Reserve crashkernel memory region Mohan Kumar M
2006-04-28 7:06 ` Michael Neuling [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=20060428070704.4AD0A679F5@ozlabs.org \
--to=mikey@neuling$(echo .)org \
--cc=fastboot@osdl$(echo .)org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=mohan@in$(echo .)ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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