[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAE9FiQXOdMS1L2XOeq+D2SV8-Ey0CTLEyRO30oxCthFbSSeMDQ@mail.gmail.com>
Date: Tue, 10 Mar 2015 12:29:50 -0700
From: Yinghai Lu <yinghai@...nel.org>
To: Borislav Petkov <bp@...e.de>, "H. Peter Anvin" <hpa@...or.com>,
Ingo Molnar <mingo@...hat.com>
Cc: Matt Fleming <matt.fleming@...el.com>,
Kees Cook <keescook@...omium.org>, Baoquan He <bhe@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Jiri Kosina <jkosina@...e.cz>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>
Subject: Re: [PATCH v3 3/7] x86, boot: Don't overlap VO with ZO data
On Tue, Mar 10, 2015 at 8:48 AM, Borislav Petkov <bp@...e.de> wrote:
> On Tue, Mar 10, 2015 at 08:42:40AM -0700, Yinghai Lu wrote:
>> In arch/x86/boot/header.S, we already use VO and ZO.
>> So please keep on using them, and don't introduce "kernel proper" etc.
>
> So you're suggesting commit messages should use variable names and
> prefixes from the code instead of being human-readable?
Now we have
vmlinux ===> VO or kernel, that is output/init_size in misc.c
arch/x86/boot/compressed/vmlinux.bin.xz ==> compressed kernel. that
is input/input_len in misc.c
arch/x86/boot/compressed/vmllinux ==> ZO,
arch/x86/boot/setup + ZO is bzImage.
I really think we should not use
"compressed kernel" for arch/x86/boot/compressed/vmlinux
that should stand for compressed vmlinux.
VO/ZO should be better thatn "kernel proper"/'compressed kernel"
for vmlinux/"arch/x86/boot/compressed/vmlinux" ?
Peter/Ingo, How to you think about that?
Thanks
Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists