From: Simon Horman <horms@verge.net.au>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Haren Myneni <hbabu@us.ibm.com>,
kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v7 0/7] kexec: put bzImage and ramdisk above 4G for x86 64bit
Date: Fri, 25 Jan 2013 18:08:18 +0900 [thread overview]
Message-ID: <20130125090818.GF30990@verge.net.au> (raw)
In-Reply-To: <1359060264-10671-1-git-send-email-yinghai@kernel.org>
On Thu, Jan 24, 2013 at 12:44:17PM -0800, Yinghai Lu wrote:
> Now we have limit kdump reserved under 896M, because kexec has the limitation.
> and also bzImage need to stay under 4g.
>
> kernel parts changes could be found at:
> git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-x86-boot
>
> here patches are for kexec tools to load bzImage and ramdisk above 4G
> acccording to new added boot header fields.
>
> -v3: address review from Eric to use locate_hole at first.
> use xloadflags instead.
> -v4: remove the restriction about bzImage not crossing GB boundary.
> add real-mode fix for bzImage.
> add --entry-32bit and --real-mode for skip bzImage64.
> -v5: use USE_EXT_BOOT_PARAMS bit in xloadflags.
> -v6: use sentinel instead of USE_EXT_BOOT_PARAMS.
> add crashkernel_low support
> -v7: Separate bootloader id setting in another patch
Hi Yinghai, Hi All,
my current thinking with regards to this is that I would like to take
these changes into the kexec-tools tree once there is consensus and
kernel portions have been accepted. If that makes sense please let me know
when those conditions have been met. Otherwise lets discuss a different
strategy.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-01-25 9:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 20:44 [PATCH v7 0/7] kexec: put bzImage and ramdisk above 4G for x86 64bit Yinghai Lu
2013-01-24 20:44 ` [PATCH v7 1/7] kexec, x86: add boot header member for version 2.12 Yinghai Lu
2013-01-24 20:44 ` [PATCH v7 2/7] kexec, x86: clean boot_params area for entry-32bit path Yinghai Lu
2013-01-24 20:44 ` [PATCH v7 3/7] kexec, x86: Fix bzImage real-mode booting Yinghai Lu
2013-01-24 20:44 ` [PATCH v7 4/7] kexec, x86: put ramdisk/cmd_line above 4G for 64bit bzImage Yinghai Lu
2013-01-24 20:44 ` [PATCH v7 5/7] kexec, x86: set booloader id in setup_header Yinghai Lu
2013-01-24 20:44 ` [PATCH v7 6/7] kexec, x86_64: Load bzImage64 above 4G Yinghai Lu
2013-01-24 20:44 ` [PATCH v7 7/7] kexec, x86: handle Crash low kernel range Yinghai Lu
2013-01-25 9:08 ` Simon Horman [this message]
2013-01-25 15:48 ` [PATCH v7 0/7] kexec: put bzImage and ramdisk above 4G for x86 64bit Yinghai Lu
2013-01-28 0:49 ` Simon Horman
2013-01-28 2:39 ` Yinghai Lu
2013-02-22 4:12 ` Yinghai Lu
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=20130125090818.GF30990@verge.net.au \
--to=horms@verge.net.au \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=vgoyal@redhat.com \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox