From: Daniel Kiper <daniel.kiper@oracle.com>
To: 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,
hpa@zytor.com, jgross@suse.com, konrad.wilk@oracle.com,
mingo@redhat.com, tglx@linutronix.de
Subject: [PATCH 0/4] x86/xen/efi: Initialize UEFI secure boot state during dom0 boot
Date: Tue, 9 Jan 2018 15:22:21 +0100 [thread overview]
Message-ID: <1515507745-17391-1-git-send-email-daniel.kiper@oracle.com> (raw)
Hi,
Initialize UEFI secure boot state during dom0 boot. Otherwise the kernel
may not even know that it runs on secure boot enabled platform.
Daniel
arch/x86/xen/Makefile | 4 +++-
arch/x86/xen/efi.c | 14 +++++++++++++
drivers/firmware/efi/libstub/secureboot-core.c | 77 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/firmware/efi/libstub/secureboot.c | 66 +++++------------------------------------------------------
4 files changed, 99 insertions(+), 62 deletions(-)
Daniel Kiper (4):
efi/stub: Extract efi_get_secureboot() to separate file
x86/xen/efi: Initialize boot_params.secure_boot in xen_efi_init()
efi: Tweak efi_get_secureboot() and its data section assignment
efi: Rename efi_get_secureboot() to __efi_get_secureboot() and make it static
next reply other threads:[~2018-01-09 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 14:22 Daniel Kiper [this message]
2018-01-09 14:22 ` [PATCH 1/4] efi/stub: Extract efi_get_secureboot() to separate file Daniel Kiper
2018-01-09 14:22 ` [PATCH 2/4] x86/xen/efi: Initialize boot_params.secure_boot in xen_efi_init() Daniel Kiper
2018-01-09 14:22 ` [PATCH 3/4] efi: Tweak efi_get_secureboot() and its data section assignment Daniel Kiper
2018-01-09 14:22 ` [PATCH 4/4] efi: Rename efi_get_secureboot() to __efi_get_secureboot() and make it static Daniel Kiper
2018-01-11 12:51 ` [PATCH 0/4] x86/xen/efi: Initialize UEFI secure boot state during dom0 boot Ard Biesheuvel
2018-01-12 11:24 ` Daniel Kiper
2018-01-23 19:23 ` Ard Biesheuvel
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=1515507745-17391-1-git-send-email-daniel.kiper@oracle.com \
--to=daniel.kiper@oracle.com \
--cc=ard.biesheuvel@linaro.org \
--cc=boris.ostrovsky@oracle.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®