From: Robbie Harwood <rharwood@redhat.com>
To: Stefan Berger <stefanb@linux.ibm.com>,
grub-devel@gnu.org, dkiper@net-space.pl
Cc: development@efficientek.com, dja@axtens.net,
sudhakar@linux.ibm.com, nasastry@in.ibm.com,
avnish@imap.linux.ibm.com, Stefan Berger <stefanb@linux.ibm.com>,
Eric Snowberg <eric.snowberg@oracle.com>,
Daniel Kiper <daniel.kiper@oracle.com>
Subject: Re: [PATCH v4 6/6] ibmvtpm: Add support for trusted boot using a vTPM 2.0
Date: Mon, 06 Feb 2023 15:12:47 -0500 [thread overview]
Message-ID: <jlgo7q6ft8g.fsf@redhat.com> (raw)
In-Reply-To: <20230206150325.3756840-7-stefanb@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
Stefan Berger <stefanb@linux.ibm.com> writes:
> Add support for trusted boot using a vTPM 2.0 on the IBM IEEE1275
> PowerPC platform. With this patch grub now measures text and binary data
> into the TPM's PCRs 8 and 9 in the same way as the x86_64 platform
> does.
>
> This patch requires Daniel Axtens's patches for claiming more memory.
>
> Note: The tpm_init() function cannot be called from GRUB_MOD_INIT() since
> it does not find the device nodes upon module initialization and
> therefore the call to tpm_init() must be deferred to grub_tpm_measure().
>
> For vTPM support to work on PowerVM, system driver levels 1010.30
> or 1020.00 are required.
>
> Note: Previous versions of firmware levels with the 2hash-ext-log
> API call have a bug that, once this API call is invoked, has the
> effect of disabling the vTPM driver under Linux causing an error
> message to be displayed in the Linux kernel log. Those users will
> have to update their machines to the firmware levels mentioned
> above.
>
> Cc: Eric Snowberg <eric.snowberg@oracle.com>
> Signed-off-by: Stefan Berger <stefanb@linux.ibm.com>
> Signed-off-by: Daniel Axtens <dja@axtens.net>
> Reviewed-by: Daniel Kiper <daniel.kiper@oracle.com>
Reviewed-by: Robbie Harwood <rharwood@redhat.com>
Be well,
--Robbie
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2023-02-06 20:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 15:03 [PATCH v4 0/6] Dynamic allocation of memory regions and IBM vTPM 2.0 Stefan Berger
2023-02-06 15:03 ` [PATCH v4 1/6] ieee1275: request memory with ibm, client-architecture-support Stefan Berger
2023-02-06 15:03 ` [PATCH v4 2/6] ieee1275: drop len -= 1 quirk in heap_init Stefan Berger
2023-02-16 14:27 ` Robbie Harwood
2023-02-06 15:03 ` [PATCH v4 3/6] ieee1275: support runtime memory claiming Stefan Berger
2023-02-06 20:09 ` Robbie Harwood
2023-02-06 20:59 ` Stefan Berger
2023-02-16 14:27 ` Robbie Harwood
2023-02-06 15:03 ` [PATCH v4 4/6] ieee1275: implement vec5 for cas negotiation Stefan Berger
2023-02-06 15:03 ` [PATCH v4 5/6] Add memtool module with memory allocation stress-test Stefan Berger
2023-02-06 15:03 ` [PATCH v4 6/6] ibmvtpm: Add support for trusted boot using a vTPM 2.0 Stefan Berger
2023-02-06 20:12 ` Robbie Harwood [this message]
2023-02-13 12:58 ` [PATCH v4 0/6] Dynamic allocation of memory regions and IBM " Nageswara R Sastry
2023-02-28 17:50 ` Robbie Harwood
2023-03-01 13:11 ` 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=jlgo7q6ft8g.fsf@redhat.com \
--to=rharwood@redhat.com \
--cc=avnish@imap.linux.ibm.com \
--cc=daniel.kiper@oracle.com \
--cc=development@efficientek.com \
--cc=dja@axtens.net \
--cc=dkiper@net-space.pl \
--cc=eric.snowberg@oracle.com \
--cc=grub-devel@gnu.org \
--cc=nasastry@in.ibm.com \
--cc=stefanb@linux.ibm.com \
--cc=sudhakar@linux.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.