From: Yinghai Lu <yinghai@kernel.org>
To: Simon Horman <horms@verge.net.au>,
"H. Peter Anvin" <hpa@zytor.com>, Vivek Goyal <vgoyal@redhat.com>,
Haren Myneni <hbabu@us.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: Yinghai Lu <yinghai@kernel.org>, kexec@lists.infradead.org
Subject: [PATCH v6 0/6] kexec: put bzImage and ramdisk above 4G for x86 64bit
Date: Thu, 13 Dec 2012 14:18:26 -0800 [thread overview]
Message-ID: <1355437112-9250-1-git-send-email-yinghai@kernel.org> (raw)
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
Yinghai Lu (6):
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 | 33 +++-
kexec/arch/i386/crashdump-x86.c | 21 +++
kexec/arch/i386/include/arch/options.h | 4 +-
kexec/arch/i386/kexec-bzImage.c | 81 +++++++--
kexec/arch/i386/x86-linux-setup.c | 27 ++-
kexec/arch/x86_64/Makefile | 1 +
kexec/arch/x86_64/kexec-bzImage64.c | 312 ++++++++++++++++++++++++++++++++
kexec/arch/x86_64/kexec-x86_64.c | 1 +
kexec/arch/x86_64/kexec-x86_64.h | 5 +
9 files changed, 461 insertions(+), 24 deletions(-)
create mode 100644 kexec/arch/x86_64/kexec-bzImage64.c
--
1.7.10.4
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2012-12-13 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-13 22:18 Yinghai Lu [this message]
2012-12-13 22:18 ` [PATCH v6 1/6] kexec, x86: add boot header member for version 2.12 Yinghai Lu
2012-12-13 22:18 ` [PATCH v6 2/6] kexec, x86: clean boot_params area for entry-32bit path Yinghai Lu
2012-12-13 22:18 ` [PATCH v6 3/6] kexec, x86: Fix bzImage real-mode booting Yinghai Lu
2012-12-13 23:42 ` H. Peter Anvin
2012-12-14 0:06 ` Yinghai Lu
2012-12-13 22:18 ` [PATCH v6 4/6] kexec, x86: put ramdisk/cmd_line above 4G for 64bit bzImage Yinghai Lu
2012-12-13 22:18 ` [PATCH v6 5/6] kexec, x86_64: Load bzImage64 above 4G Yinghai Lu
2012-12-13 22:18 ` [PATCH v6 6/6] kexec, x86: handle Crash low kernel range Yinghai Lu
2012-12-14 0:41 ` [PATCH v6 0/6] kexec: put bzImage and ramdisk above 4G for x86 64bit H. Peter Anvin
2012-12-14 0:47 ` 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=1355437112-9250-1-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.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 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.