linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Kiper <daniel.kiper@oracle.com>,
	linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, xen-devel@lists.xenproject.org
Cc: ard.biesheuvel@linaro.org, boris.ostrovsky@oracle.com,
	bp@alien8.de, corbet@lwn.net, dave.hansen@linux.intel.com,
	luto@kernel.org, peterz@infradead.org, eric.snowberg@oracle.com,
	jgross@suse.com, kanth.ghatraju@oracle.com,
	konrad.wilk@oracle.com, mingo@redhat.com, rdunlap@infradead.org,
	ross.philipson@oracle.com, tglx@linutronix.de
Subject: Re: [PATCH v5 0/3] x86/boot: Introduce the kernel_info et consortes
Date: Tue, 5 Nov 2019 13:40:28 -0800	[thread overview]
Message-ID: <d45aa4da-57fd-757f-3f82-d88449f057ce@zytor.com> (raw)
In-Reply-To: <20191104151354.28145-1-daniel.kiper@oracle.com>

On 2019-11-04 07:13, 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.
> 
> Daniel
> 

Looks great!  Ship it!

Reviewed-by: H. Peter Anvin (Intel) <hpa@zytor.com>

	-hpa

  parent reply	other threads:[~2019-11-05 21:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-04 15:13 [PATCH v5 0/3] x86/boot: Introduce the kernel_info et consortes Daniel Kiper
2019-11-04 15:13 ` [PATCH v5 1/3] x86/boot: Introduce the kernel_info Daniel Kiper
2019-11-04 15:13 ` [PATCH v5 2/3] x86/boot: Introduce the kernel_info.setup_type_max Daniel Kiper
2019-11-08 10:09   ` Borislav Petkov
2019-11-08 10:47     ` Daniel Kiper
2019-11-08 11:07       ` Borislav Petkov
2019-11-08 12:52         ` Daniel Kiper
2019-11-08 13:03           ` Borislav Petkov
2019-11-08 13:39             ` Daniel Kiper
2019-11-04 15:13 ` [PATCH v5 3/3] x86/boot: Introduce the setup_indirect Daniel Kiper
2019-11-08 11:33   ` Borislav Petkov
2019-11-05 21:40 ` H. Peter Anvin [this message]
2019-11-06 17:03 ` [PATCH v5 0/3] x86/boot: Introduce the kernel_info et consortes Borislav Petkov
2019-11-06 17:56   ` hpa
2019-11-06 19:43     ` Borislav Petkov
2019-11-07 11:31     ` Daniel Kiper

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=d45aa4da-57fd-757f-3f82-d88449f057ce@zytor.com \
    --to=hpa@zytor.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=daniel.kiper@oracle.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=eric.snowberg@oracle.com \
    --cc=jgross@suse.com \
    --cc=kanth.ghatraju@oracle.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=ross.philipson@oracle.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    --cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).