From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jerry Snitselaar <jsnitsel@redhat.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
linux-security-module@vger.kernel.org,
Stefan Berger <stefanb@linux.ibm.com>
Subject: Re: [PATCH v9 2/2] tpm: Add support for event log pointer found in TPM2 ACPI table
Date: Tue, 7 Jul 2020 05:24:57 +0300 [thread overview]
Message-ID: <20200707022457.GD112019@linux.intel.com> (raw)
In-Reply-To: <87mu4cjixj.fsf@redhat.com>
On Mon, Jul 06, 2020 at 04:57:28PM -0700, Jerry Snitselaar wrote:
>
> Jarkko Sakkinen @ 2020-07-06 16:09 MST:
>
> > On Mon, Jul 06, 2020 at 02:19:53PM -0400, Stefan Berger wrote:
> >> From: Stefan Berger <stefanb@linux.ibm.com>
> >>
> >> In case a TPM2 is attached, search for a TPM2 ACPI table when trying
> >> to get the event log from ACPI. If one is found, use it to get the
> >> start and length of the log area. This allows non-UEFI systems, such
> >> as SeaBIOS, to pass an event log when using a TPM2.
> >>
> >> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> >
> > Do you think that QEMU with TPM 1.2 emulator turned on would be a viable
> > way to test this?
> >
> > I'm anyway more worried about breaking existing TPM 1.2 functionality
> > and that requires only QEMU without extras.
> >
> > /Jarkko
>
> The 1.2 bits should be functionally the same as before, right?
Yes. You should be able to read event log with TPM 1.2 as before.
/Jarkko
prev parent reply other threads:[~2020-07-07 2:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-06 18:19 [PATCH v9 0/2] tpm2: Make TPM2 logs accessible for non-UEFI firmware Stefan Berger
2020-07-06 18:19 ` [PATCH v9 1/2] acpi: Extend TPM2 ACPI table with missing log fields Stefan Berger
2020-07-06 22:02 ` Jerry Snitselaar
2020-07-06 18:19 ` [PATCH v9 2/2] tpm: Add support for event log pointer found in TPM2 ACPI table Stefan Berger
2020-07-06 22:04 ` Jerry Snitselaar
2020-07-06 23:09 ` Jarkko Sakkinen
2020-07-06 23:12 ` Jarkko Sakkinen
2020-07-06 23:55 ` Stefan Berger
2020-07-07 2:24 ` Jarkko Sakkinen
2020-07-07 3:08 ` Stefan Berger
2020-07-07 4:03 ` Jarkko Sakkinen
2020-07-07 4:09 ` Stefan Berger
2020-07-08 14:07 ` Jarkko Sakkinen
2020-07-08 14:17 ` Stefan Berger
2020-07-14 11:20 ` Jarkko Sakkinen
2020-07-14 12:09 ` Stefan Berger
2020-07-16 17:26 ` Jarkko Sakkinen
2020-07-06 23:57 ` Jerry Snitselaar
2020-07-07 2:24 ` Jarkko Sakkinen [this message]
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=20200707022457.GD112019@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jsnitsel@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=stefanb@linux.ibm.com \
--cc=stefanb@linux.vnet.ibm.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 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.