From: Daniel Kiper <daniel.kiper@oracle.com>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Cc: dpsmith@apertussolutions.com, eric.snowberg@oracle.com,
hpa@zytor.com, kanth.ghatraju@oracle.com, konrad.wilk@oracle.com,
ross.philipson@oracle.com
Subject: Re: [PATCH RFC 0/2] x86/boot: Introduce the setup_header2
Date: Wed, 5 Jun 2019 15:50:31 +0200 [thread overview]
Message-ID: <20190605135031.62grhhxn2pfbkcdg@tomti.i.net-space.pl> (raw)
In-Reply-To: <20190524095504.12894-1-daniel.kiper@oracle.com>
On Fri, May 24, 2019 at 11:55:02AM +0200, Daniel Kiper wrote:
> Hi,
>
> This change is needed to properly start the Linux kernel in Intel TXT mode and
> is a part of the TrenchBoot project (https://github.com/TrenchBoot).
>
> Daniel
>
> Documentation/x86/boot.txt | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
> arch/x86/Kconfig | 7 +++++++
> arch/x86/boot/Makefile | 2 +-
> arch/x86/boot/compressed/Makefile | 5 +++--
> arch/x86/boot/compressed/setup_header2.S | 18 ++++++++++++++++++
> arch/x86/boot/compressed/sl_stub.S | 28 ++++++++++++++++++++++++++++
> arch/x86/boot/header.S | 3 ++-
> arch/x86/boot/tools/build.c | 8 ++++++++
> arch/x86/include/uapi/asm/bootparam.h | 1 +
> 9 files changed, 123 insertions(+), 4 deletions(-)
>
> Daniel Kiper (2):
> x86/boot: Introduce the setup_header2
> x86/boot: Introduce dummy MLE header
Ping?
Daniel
next prev parent reply other threads:[~2019-06-05 13:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 9:55 [PATCH RFC 0/2] x86/boot: Introduce the setup_header2 Daniel Kiper
2019-05-24 9:55 ` [PATCH RFC 1/2] " Daniel Kiper
2019-06-06 22:06 ` H. Peter Anvin
2019-06-14 11:06 ` Daniel Kiper
2019-05-24 9:55 ` [PATCH RFC 2/2] x86/boot: Introduce dummy MLE header Daniel Kiper
2019-06-05 13:50 ` Daniel Kiper [this message]
2019-06-05 14:01 ` [PATCH RFC 0/2] x86/boot: Introduce the setup_header2 Konrad Rzeszutek Wilk
2019-06-06 11:51 ` Daniel Kiper
2019-06-06 17:30 ` Konrad Rzeszutek Wilk
2019-06-06 17:46 ` 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=20190605135031.62grhhxn2pfbkcdg@tomti.i.net-space.pl \
--to=daniel.kiper@oracle.com \
--cc=dpsmith@apertussolutions.com \
--cc=eric.snowberg@oracle.com \
--cc=hpa@zytor.com \
--cc=kanth.ghatraju@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ross.philipson@oracle.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.