From: Vivek Goyal <vgoyal@redhat.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>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH v3 4/4] kexec, x86_64: Load bzImage64 above 4G
Date: Wed, 21 Nov 2012 15:12:29 -0500 [thread overview]
Message-ID: <20121121201229.GJ13114@redhat.com> (raw)
In-Reply-To: <CAE9FiQWMo1mxNyk=co9rL3ST0GTCjniVJQKUNyT8_6MrbYNJHQ@mail.gmail.com>
On Wed, Nov 21, 2012 at 12:09:04PM -0800, Yinghai Lu wrote:
> On Wed, Nov 21, 2012 at 12:00 PM, Vivek Goyal <vgoyal@redhat.com> wrote:
> > On Wed, Nov 21, 2012 at 11:50:56AM -0800, Yinghai Lu wrote:
> >
> > [..]
> >> > So how do I force a 16bit or 32bit entry using a bzImage64?
> >>
> >> kexec -t bzImage -l ....
> >> will load low and use 32bit entry.
> >>
> >
> > Ok, so user needs to enforce image type (using -t option) to bzImage
> > (for a bzImage which supports 64bit entry point) to be able to use
> > 32bit entry.
> >
> > I think a better option is that bzImage64 loader parses the user specified
> > entry options and call into 32bit bzImage loader if user is asking for 32bit
> > or 16bit entry. For 16bit, we already have option --real-mode option. May
> > be we need to introduce another one for forcing 32bit entry, say --entry-32bit
> > or --protected-mode (whatever makes sense).
>
> that is doable.
>
> add checking entry-32bit and real-mode checking in kexec-bzImage64.c
> and bail early to leave kexec-bzImage.c to take over.
Or actually can we do reverse. Do not introduce new image format
bzImage64. In existing bzImage loader if bzImage version is greater
than 0x020c (or whatever version has 64bit entry extension), just
call into load_bzImage64().
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2012-11-21 20:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 7:31 [PATCH v3 0/4] kexec: put bzImage and ramdisk above 4G for x86 64bit Yinghai Lu
2012-11-21 7:31 ` [PATCH v3 1/4] kexec, x86: add boot header member for version 2.12 Yinghai Lu
2012-11-21 7:31 ` [PATCH v3 2/4] kexec, x86: put ramdisk high for 64bit bzImage Yinghai Lu
2012-11-21 7:31 ` [PATCH v3 3/4] kexec, x86: set ext_cmd_line_ptr when boot_param is above 4g Yinghai Lu
2012-11-21 7:31 ` [PATCH v3 4/4] kexec, x86_64: Load bzImage64 above 4G Yinghai Lu
2012-11-21 14:37 ` Vivek Goyal
2012-11-21 17:24 ` H. Peter Anvin
2012-11-21 19:54 ` Yinghai Lu
2012-11-21 19:56 ` H. Peter Anvin
2012-11-21 20:01 ` Yinghai Lu
2012-11-21 20:16 ` H. Peter Anvin
2012-11-21 20:47 ` Yinghai Lu
2012-11-21 20:56 ` H. Peter Anvin
2012-11-21 23:34 ` H. Peter Anvin
2012-11-22 5:52 ` Yinghai Lu
2012-11-21 14:50 ` Vivek Goyal
2012-11-21 19:50 ` Yinghai Lu
2012-11-21 19:52 ` H. Peter Anvin
2012-11-21 19:57 ` Yinghai Lu
2012-11-21 20:00 ` Vivek Goyal
2012-11-21 20:09 ` Yinghai Lu
2012-11-21 20:12 ` Vivek Goyal [this message]
2012-11-21 20:17 ` Yinghai Lu
2012-11-21 20:07 ` Vivek Goyal
2012-11-22 11:39 ` Eric W. Biederman
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=20121121201229.GJ13114@redhat.com \
--to=vgoyal@redhat.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--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