public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org,
	Matt Fleming <matt.fleming@intel.com>
Subject: Re: [PATCH v2 03/13] x86: Add macro for 64bit entry startup_64
Date: Tue, 20 Nov 2012 13:12:26 -0800	[thread overview]
Message-ID: <50ABF23A.7020305@zytor.com> (raw)
In-Reply-To: <CAE9FiQUjZG_UakYdpxEf8_EHQ4UBo6GK1E_g4wDY576MFcVL4Q@mail.gmail.com>

On 11/20/2012 12:55 PM, Yinghai Lu wrote:
> On Tue, Nov 20, 2012 at 12:44 PM, H. Peter Anvin <hpa@zytor.com> wrote:
>> I don't see any point in three flags here.  Let's stick to one flag; then it fits in the existing boot_flags field.
>
> the magic AA55
>
> boot/header.S:boot_flag:        .word 0xAA55
>
> if change that to other value, would it break existing boot loader?
> aka old boot loader could boot the new bzImage anymore.
>

Sorry, I meant loadflags.

This is a read flag and so should be low, bit 1 presumably.

On the other hand, the read flags in loadflags has not been modified for 
a very long time, and there is a serious risk that some broken 
bootloader might be doing a full byte comparison.

relocatable_kernel really should have been a flag, but it is now defined 
as a comparison with zero.  As such, and in an effort to minimize the 
growth of struct setup_header (it is limited to little over 128 bytes 
long) I suggest we redefine the 16-byte field at offset 0x236 as a new 
flags field.  We still only need one flag, though.

Backwards compatibility is so much fun.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2012-11-20 21:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-18  7:09 [PATCH v2 00/13] x86, boot, 64bit: Add support for loading ramdisk and bzImage high Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 01/13] x86, boot: move verify_cpu.S after 0x200 Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 02/13] x86, boot: Move lldt/ltr out of 64bit code section Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 03/13] x86: Add macro for 64bit entry startup_64 Yinghai Lu
2012-11-19 22:42   ` H. Peter Anvin
2012-11-19 22:53     ` Yinghai Lu
2012-11-19 23:13       ` H. Peter Anvin
2012-11-19 23:46         ` Yinghai Lu
2012-11-19 23:55           ` H. Peter Anvin
2012-11-20  0:39             ` Yinghai Lu
2012-11-20 19:20               ` Yinghai Lu
2012-11-20 20:44                 ` H. Peter Anvin
2012-11-20 20:55                   ` Yinghai Lu
2012-11-20 21:12                     ` H. Peter Anvin [this message]
2012-11-21  0:20                       ` Yinghai Lu
2012-11-21  0:28                         ` H. Peter Anvin
2012-11-21  0:32                           ` Yinghai Lu
2012-11-21  0:34                             ` Yinghai Lu
2012-11-21  0:45                               ` H. Peter Anvin
2012-11-18  7:09 ` [PATCH v2 04/13] x86, 64bit: set extra ident page table for whole kernel range Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 05/13] x86, 64bit: add support for loading kernel above 512G Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 06/13] x86: Merge early_reserve_initrd for 32bit and 64bit Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 07/13] x86: add get_ramdisk_image/size Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 08/13] x86, boot: add get_cmd_line_ptr() Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 09/13] x86, boot: Don't check if cmd_line_ptr is accessible in misc/decompressor() Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 10/13] x86, boot: update cmd_line_ptr to unsigned long Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 11/13] x86: use io_remap to access real_mode_data Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 12/13] x86, boot: add fields to support load bzImage and ramdisk high Yinghai Lu
2012-11-18  7:09 ` [PATCH v2 13/13] x86: remove 1024g limitation for kexec buffer on 64bit 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=50ABF23A.7020305@zytor.com \
    --to=hpa@zytor.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --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