From: Stefan Berger <stefanb@linux.ibm.com>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Stefan Berger <stefanb@linux.vnet.ibm.com>,
linux-integrity@vger.kernel.org
Cc: aik@ozlabs.ru, david@gibson.dropbear.id.au,
linux-kernel@vger.kernel.org, nayna@linux.vnet.ibm.com,
gcwilson@linux.ibm.com, jgg@ziepe.ca
Subject: Re: [PATCH v6 0/3] Enable vTPM 2.0 for the IBM vTPM driver
Date: Thu, 5 Mar 2020 08:56:29 -0500 [thread overview]
Message-ID: <3e3a37ea-a1e7-e960-a892-1a5a4b146d30@linux.ibm.com> (raw)
In-Reply-To: <deab5eab2de31a1116e16e025c94fbc6f1d0d742.camel@linux.intel.com>
On 3/5/20 6:20 AM, Jarkko Sakkinen wrote:
> On Wed, 2020-03-04 at 08:22 -0500, Stefan Berger wrote:
>> From: Stefan Berger <stefanb@linux.ibm.com>
>>
>> QEMU 5.0 will support the PAPR vTPM device model for TPM 1.2 and TPM 2.0.
>> This series of patches enables vTPM 2.0 support for the IBM vTPM driver.
> BTW, what is PAPR vTPM device model? Is it something that is used
> generally for vTPM's or just in IBM context?
It's an IBM pSeries specification. The device model is only used on pSeries.
Stefan
>
> /Jarkko
>
prev parent reply other threads:[~2020-03-05 13:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 13:22 [PATCH v6 0/3] Enable vTPM 2.0 for the IBM vTPM driver Stefan Berger
2020-03-04 13:22 ` [PATCH v6 1/3] tpm: of: Handle IBM,vtpm20 case when getting log parameters Stefan Berger
2020-03-10 22:56 ` kbuild test robot
2020-03-11 12:58 ` Stefan Berger
2020-03-04 13:22 ` [PATCH v6 2/3] tpm: ibmvtpm: Wait for buffer to be set before proceeding Stefan Berger
2020-03-05 11:21 ` Jarkko Sakkinen
2020-03-04 13:22 ` [PATCH v6 3/3] tpm: ibmvtpm: Add support for TPM2 Stefan Berger
2020-03-05 11:21 ` Jarkko Sakkinen
2020-03-05 13:58 ` Stefan Berger
2020-03-06 18:33 ` Jarkko Sakkinen
2020-03-06 18:51 ` Stefan Berger
2020-03-07 11:09 ` Jarkko Sakkinen
2020-03-10 21:16 ` Nayna
2020-03-05 11:20 ` [PATCH v6 0/3] Enable vTPM 2.0 for the IBM vTPM driver Jarkko Sakkinen
2020-03-05 13:56 ` Stefan Berger [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=3e3a37ea-a1e7-e960-a892-1a5a4b146d30@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=aik@ozlabs.ru \
--cc=david@gibson.dropbear.id.au \
--cc=gcwilson@linux.ibm.com \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nayna@linux.vnet.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 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).