From: Dave Young <dyoung@redhat.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Simon Horman <horms@verge.net.au>,
kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v9 0/7] kexec: put bzImage and ramdisk above 4G for x86 64bit
Date: Tue, 26 Feb 2013 17:18:58 +0800 [thread overview]
Message-ID: <512C7E02.8050602@redhat.com> (raw)
In-Reply-To: <1361506076-13112-1-git-send-email-yinghai@kernel.org>
On 02/22/2013 12:07 PM, Yinghai Lu wrote:
> Now we have limit kdump reserved under 896M, because kexec has the limitation.
> and also bzImage need to stay under 4g.
I think the kernel patches has been merged in linus tree, I got a crash
memory address above 4G during my test, kexec tools need this patchset
to load the 2nd kernel..
BTW, Simon, do you have plan to release the 2.0.4?
>
> kernel parts changes get merged to linus tree already.
>
> here patches are for kexec tools to load bzImage and ramdisk above 4G
> acccording to new added boot header fields.
>
> it will only load high with 64bit kernel with 2.12 setup header.
>
> -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
> -v8: update for CAN_BE_LOADED_ABOVE_4G is changed to bit1.
> also make it appliable to current kexec-tools devel tree.
> -v9: only copy setup_header when it is not with real_mode_entry.
>
> Yinghai Lu (7):
> kexec, x86: set booloader id in setup_header
> kexec, x86: add boot header member for version 2.12
> kexec, x86: clean boot_params area for entry-32bit path
> kexec, x86: Fix bzImage real-mode booting
> kexec, x86: put ramdisk/cmd_line above 4G for 64bit bzImage
> kexec, x86_64: Load bzImage64 above 4G
> kexec, x86: handle Crash low kernel range
>
> include/x86/x86-linux.h | 27 ++-
> kexec/arch/i386/crashdump-x86.c | 21 +++
> kexec/arch/i386/include/arch/options.h | 4 +-
> kexec/arch/i386/kexec-bzImage.c | 76 ++++++--
> kexec/arch/i386/x86-linux-setup.c | 38 ++--
> kexec/arch/i386/x86-linux-setup.h | 15 +-
> kexec/arch/x86_64/Makefile | 1 +
> kexec/arch/x86_64/kexec-bzImage64.c | 304 ++++++++++++++++++++++++++++++++
> kexec/arch/x86_64/kexec-x86_64.c | 1 +
> kexec/arch/x86_64/kexec-x86_64.h | 5 +
> 10 files changed, 460 insertions(+), 32 deletions(-)
> create mode 100644 kexec/arch/x86_64/kexec-bzImage64.c
>
--
Thanks
Dave
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-02-26 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 4:07 [PATCH v9 0/7] kexec: put bzImage and ramdisk above 4G for x86 64bit Yinghai Lu
2013-02-22 4:07 ` [PATCH v9 1/7] kexec, x86: set booloader id in setup_header Yinghai Lu
2013-02-22 4:07 ` [PATCH v9 2/7] kexec, x86: add boot header member for version 2.12 Yinghai Lu
2013-02-22 4:07 ` [PATCH v9 3/7] kexec, x86: clean boot_params area for entry-32bit path Yinghai Lu
2013-02-22 4:07 ` [PATCH v9 4/7] kexec, x86: Fix bzImage real-mode booting Yinghai Lu
2013-02-22 4:07 ` [PATCH v9 5/7] kexec, x86: put ramdisk/cmd_line above 4G for 64bit bzImage Yinghai Lu
2013-02-22 4:07 ` [PATCH v9 6/7] kexec, x86_64: Load bzImage64 above 4G Yinghai Lu
2013-02-22 4:07 ` [PATCH v9 7/7] kexec, x86: handle Crash low kernel range Yinghai Lu
2013-02-26 9:18 ` Dave Young [this message]
2013-03-05 1:34 ` [PATCH v9 0/7] kexec: put bzImage and ramdisk above 4G for x86 64bit Simon Horman
2013-03-05 1:39 ` Simon Horman
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=512C7E02.8050602@redhat.com \
--to=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.