From: Xinwei Kong <kong.kongxinwei@hisilicon.com>
To: <ard.biesheuvel@linaro.org>, <mingo@kernel.org>,
<will@kernel.org>, <kstewart@linuxfoundation.org>,
<tglx@linutronix.de>, <steve.capper@arm.com>,
<linux-efi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <linuxarm@huawei.com>, <zoucao@linux.alibaba.com>,
<kong.kongxinwei@hisilicon.com>
Subject: [PATCH] EFI/stub: tpm: enable tpm eventlog function for ARM64 platform
Date: Tue, 5 Nov 2019 16:29:24 +0800 [thread overview]
Message-ID: <20191105082924.289-1-kong.kongxinwei@hisilicon.com> (raw)
this patch gets tpm eventlog information such as device boot status,event guid
and so on, which will be from bios stage. it use "efi_retrieve_tpm2_eventlog"
functions to get it for ARM64 platorm.
Signed-off-by: Xinwei Kong <kong.kongxinwei@hisilicon.com>
Signed-off-by: Zou Cao <zoucao@linux.alibaba.com>
---
drivers/firmware/efi/libstub/arm-stub.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/firmware/efi/libstub/arm-stub.c b/drivers/firmware/efi/libstub/arm-stub.c
index c382a48..37c8f81 100644
--- a/drivers/firmware/efi/libstub/arm-stub.c
+++ b/drivers/firmware/efi/libstub/arm-stub.c
@@ -139,6 +139,8 @@ unsigned long efi_entry(void *handle, efi_system_table_t *sys_table,
if (status != EFI_SUCCESS)
goto fail;
+ efi_retrieve_tpm2_eventlog(sys_table);
+
/*
* Get a handle to the loaded image protocol. This is used to get
* information about the running image, such as size and the command
--
2.7.4
next reply other threads:[~2019-11-05 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 8:29 Xinwei Kong [this message]
2019-11-06 14:56 ` [PATCH] EFI/stub: tpm: enable tpm eventlog function for ARM64 platform Ard Biesheuvel
2019-11-06 14:59 ` Ard Biesheuvel
2019-11-07 8:03 ` kongxinwei
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=20191105082924.289-1-kong.kongxinwei@hisilicon.com \
--to=kong.kongxinwei@hisilicon.com \
--cc=ard.biesheuvel@linaro.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mingo@kernel.org \
--cc=steve.capper@arm.com \
--cc=tglx@linutronix.de \
--cc=will@kernel.org \
--cc=zoucao@linux.alibaba.com \
/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).