From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Haren Myneni <hbabu@us.ibm.com>,
Simon Horman <horms@verge.net.au>,
kexec@lists.infradead.org,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH v4 6/6] kexec, x86_64: Load bzImage64 above 4G
Date: Sat, 24 Nov 2012 16:42:29 -0800 [thread overview]
Message-ID: <50B16975.7010402@zytor.com> (raw)
In-Reply-To: <CAE9FiQXhz8cA7d0a8UA4YWBScrZnVnVAQTHqN3F0_f5omi1o1A@mail.gmail.com>
On 11/24/2012 04:38 PM, Yinghai Lu wrote:
> On Sat, Nov 24, 2012 at 12:47 PM, Yinghai Lu <yinghai@kernel.org> wrote:
>> need to check xloadflags to see the bzImage is for 64bit relocatable.
>>
>> -v2: add kexec-bzImage64.c according to Eric.
>> -v3: don't need to purgatory under 2g after Eric's change to purgatory code.
>> -v4: use locate_hole find position first then add_buffer... suggested by Eric
>> add buffer for kernel image at last to make kexec-load faster.
>> use xloadflags in setup_header to tell if is bzImage64.
>> remove not cross GB boundary searching.
>> add --entry-32bit and --real-mode for skipping bzImage64.
>
> -v5: attached. that is using USE_EXT_BOOT_PARAMS bit in xloadflags
>
Yinghai, revving the patch is pointless until we agree on the proper
architectural direction.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2012-11-25 0:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 20:47 [PATCH v4 0/6] kexec: put bzImage and ramdisk above 4G for x86 64bit Yinghai Lu
2012-11-24 20:47 ` [PATCH v4 1/6] kexec, x86: clean boot_params area for entry-32bit path Yinghai Lu
2012-11-24 20:47 ` [PATCH v4 2/6] kexec, x86: Fix bzImage real-mode booting Yinghai Lu
2012-11-24 20:47 ` [PATCH v4 3/6] kexec, x86: add boot header member for version 2.12 Yinghai Lu
2012-11-24 20:47 ` [PATCH v4 4/6] kexec, x86: put ramdisk high for 64bit bzImage Yinghai Lu
2012-11-25 0:37 ` Yinghai Lu
2012-11-24 20:47 ` [PATCH v4 5/6] kexec, x86: set ext_cmd_line_ptr when boot_param is above 4g Yinghai Lu
2012-11-24 20:47 ` [PATCH v4 6/6] kexec, x86_64: Load bzImage64 above 4G Yinghai Lu
2012-11-25 0:38 ` Yinghai Lu
2012-11-25 0:42 ` H. Peter Anvin [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=50B16975.7010402@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=horms@verge.net.au \
--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