qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Berger <stefanb@linux.ibm.com>
To: Auger Eric <eric.auger@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>,
	Igor Mammedov <imammedo@redhat.com>
Cc: peter.maydell@linaro.org, drjones@redhat.com, mst@redhat.com,
	qemu-devel@nongnu.org, shannon.zhaosl@gmail.com,
	qemu-arm@nongnu.org, marcandre.lureau@redhat.com,
	philmd@redhat.com, ardb@kernel.org, eric.auger.pro@gmail.com
Subject: Re: [PATCH v4 1/5] acpi: Convert build_tpm2() to build_append* API
Date: Fri, 19 Jun 2020 07:19:51 -0400	[thread overview]
Message-ID: <ce60f439-fd2a-a72b-f004-44a01f4c5bdf@linux.ibm.com> (raw)
In-Reply-To: <44663542-8352-2398-a297-3e1fe7f4bfd5@redhat.com>

On 6/19/20 5:43 AM, Auger Eric wrote:
> Hi Laszlo,
>
> On 6/19/20 11:38 AM, Laszlo Ersek wrote:
>> On 06/18/20 09:50, Auger Eric wrote:
>>> Hi Stefan, Igor,
>>>
>>> On 6/16/20 4:11 PM, Stefan Berger wrote:
>>>> On 6/16/20 8:33 AM, Igor Mammedov wrote:
>>>>> nevertheless looks like faithfull conversion,
>>>>> btw why you didn't drop Acpi20TPM2 structure definition?
>>>>>
>>>> If we get rid of the table we should keep a reference to this document,
>>>> table 7: "TCG ACPI Specification; Family 1.2 and 2.0; Level 00 Revision
>>>> 00.37, December 19, 2014"
>>>>
>>>> https://trustedcomputinggroup.org/wp-content/uploads/TCG_ACPIGeneralSpecification_1-10_0-37-Published.pdf
>>>>
>>>>
>>>>
>>> Further looking at this spec, the log_area_minimum_length and
>>> log_area_start_address only are described in
>>> - Table 2 (TCG Hardware InterfaceDescription Table Format for TPM 1.2
>>> Clients)
>>> - Table 4 (TCG Hardware Interface Description Table Format for TPM 1.2
>>> Servers)
>>> but not in Table 7, ie. not for TPM 2.0.
>>>
>>> Are they really needed for TPM2 or what do I miss?
>> (side comment:
>>
>> LASA and LAML are optional with TPM-2.0. From the discussion at
>> <https://bugzilla.tianocore.org/show_bug.cgi?id=978>.


They are needed for (x86) BIOS, such as SeaBIOS, not for UEFI, though. I 
do not know about ARM.


> Thank you for the pointer and info. I failed to find this info in the
> spec. Given the risk of confusion, I would personally keep struct
> Acpi20TPM2 and maybe add a comment. Stefan?

Either way is fine with me for as long as we know where to find the 
layout of the structure.

   Stefan

>
> Thanks
>
> Eric
>> )
>>
>> Thanks
>> Laszlo
>>



  reply	other threads:[~2020-06-19 11:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-11 13:59 [PATCH v4 0/5] vTPM/aarch64 ACPI support Eric Auger
2020-06-11 13:59 ` [PATCH v4 1/5] acpi: Convert build_tpm2() to build_append* API Eric Auger
2020-06-11 14:25   ` Stefan Berger
2020-06-11 14:49     ` Auger Eric
2020-06-11 14:54     ` Auger Eric
2020-06-16 12:06     ` Igor Mammedov
2020-06-11 15:19   ` Stefan Berger
2020-06-11 16:13     ` Auger Eric
2020-06-16 12:33   ` Igor Mammedov
2020-06-16 14:03     ` Auger Eric
2020-06-16 14:11     ` Stefan Berger
2020-06-18  7:50       ` Auger Eric
2020-06-19  9:38         ` Laszlo Ersek
2020-06-19  9:43           ` Auger Eric
2020-06-19 11:19             ` Stefan Berger [this message]
2020-06-22  9:39               ` Igor Mammedov
2020-06-22  9:47                 ` Auger Eric
2020-06-22 12:14                   ` Igor Mammedov
2020-06-22 12:24                     ` Auger Eric
2020-06-11 13:59 ` [PATCH v4 2/5] acpi: Move build_tpm2() in the generic part Eric Auger
2020-06-11 15:14   ` Stefan Berger
2020-06-11 13:59 ` [PATCH v4 3/5] arm/acpi: TPM2 ACPI table support Eric Auger
2020-06-11 13:59 ` [PATCH v4 4/5] arm/acpi: Add the TPM2.0 device under the DSDT Eric Auger
2020-06-11 13:59 ` [PATCH v4 5/5] docs/specs/tpm: ACPI boot now supported for TPM/ARM Eric Auger

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=ce60f439-fd2a-a72b-f004-44a01f4c5bdf@linux.ibm.com \
    --to=stefanb@linux.ibm.com \
    --cc=ardb@kernel.org \
    --cc=drjones@redhat.com \
    --cc=eric.auger.pro@gmail.com \
    --cc=eric.auger@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhaosl@gmail.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).