From: "James Bottomley" <James.Bottomley@HansenPartnership.com>
To: devel@edk2.groups.io, thomas.lendacky@amd.com, public@thson.de
Cc: lersek@redhat.com, ardb+tianocore@kernel.org
Subject: Re: [edk2-devel] Problem: TPM 2.0 event log by OVMF is shown empty in Linux kernel versions after 5.8
Date: Tue, 27 Apr 2021 09:28:45 -0700 [thread overview]
Message-ID: <b2d2468a6b4dc815ccde425f5c27ab3be088c662.camel@HansenPartnership.com> (raw)
In-Reply-To: <2e82d24c-2cf2-1681-646d-3f848818ade8@amd.com>
On Tue, 2021-04-27 at 09:00 -0500, Lendacky, Thomas wrote:
> On 4/27/21 2:40 AM, Thore Sommer via groups.io wrote:
> > > I don't confirm this. I have Linux version 5.12.0-rc5+ installed
> > > and I
> > > see the attached in my binary_bios_measurements (I've run it
> > > through
> > > tpm2-eventlog so you can see the actual events).
> > Ok that is interesting.
> >
> > Here are the steps to reproduce my findings.
> > Necessary tools: Build chain for edk2, swtpm 0.5.2 and qemu 5.2.0
> >
> > 1. Build OVMF from edk2-stable202102 with
> > -a X64 -a IA32 \
> > -b RELEASE \
> > -D NETWORK_IP6_ENABLE \
> > -D TPM_ENABLE \
>
> Shouldn't you also have '-D TPM_CONFIG_ENABLE' ?
You only need that if you want the TPM configuration option for the
bios menu. Without it the TPM should self configure ... I tried it
without and it still works for me (produces the bios log).
James
next prev parent reply other threads:[~2021-04-27 16:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 19:56 Problem: TPM 2.0 event log by OVMF is shown empty in Linux kernel versions after 5.8 Thore Sommer
2021-04-26 23:44 ` [edk2-devel] " James Bottomley
2021-04-27 7:40 ` Thore Sommer
2021-04-27 14:00 ` Lendacky, Thomas
2021-04-27 15:35 ` Thore Sommer
2021-04-27 16:28 ` James Bottomley [this message]
2021-04-28 11:47 ` Laszlo Ersek
2021-04-28 14:56 ` Thore Sommer
2021-04-28 17:19 ` James Bottomley
2021-04-28 20:31 ` Thore Sommer
2021-04-28 22:03 ` James Bottomley
2021-04-29 8:20 ` Thore Sommer
2021-04-29 9:43 ` Thore Sommer
2021-04-30 15:51 ` Laszlo Ersek
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-list 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=b2d2468a6b4dc815ccde425f5c27ab3be088c662.camel@HansenPartnership.com \
--to=devel@edk2.groups.io \
/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