[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191106170333.GD28380@zn.tnic>
Date: Wed, 6 Nov 2019 18:03:33 +0100
From: Borislav Petkov <bp@...en8.de>
To: Daniel Kiper <daniel.kiper@...cle.com>
Cc: linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
x86@...nel.org, xen-devel@...ts.xenproject.org,
ard.biesheuvel@...aro.org, boris.ostrovsky@...cle.com,
corbet@....net, dave.hansen@...ux.intel.com, luto@...nel.org,
peterz@...radead.org, eric.snowberg@...cle.com, hpa@...or.com,
jgross@...e.com, kanth.ghatraju@...cle.com, konrad.wilk@...cle.com,
mingo@...hat.com, rdunlap@...radead.org, ross.philipson@...cle.com,
tglx@...utronix.de
Subject: Re: [PATCH v5 0/3] x86/boot: Introduce the kernel_info et consortes
On Mon, Nov 04, 2019 at 04:13:51PM +0100, Daniel Kiper wrote:
> Hi,
>
> Due to very limited space in the setup_header this patch series introduces new
> kernel_info struct which will be used to convey information from the kernel to
> the bootloader. This way the boot protocol can be extended regardless of the
> setup_header limitations. Additionally, the patch series introduces some
> convenience features like the setup_indirect struct and the
> kernel_info.setup_type_max field.
That's all fine and dandy but I'm missing an example about what that'll
be used for, in practice.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists