From: "Tu Dinh" <ngoc-tu.dinh@vates.tech>
To: "Andrew Cooper" <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Cc: "Jan Beulich" <jbeulich@suse.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Daniel Smith" <dpsmith@apertussolutions.com>
Subject: Re: [PATCH] acpi: Set TPM2 LAML to actual log area size
Date: Wed, 05 Nov 2025 00:02:42 +0000 [thread overview]
Message-ID: <e6dbb09f-e7a3-40e1-83b4-0e0904dfbc1c@vates.tech> (raw)
In-Reply-To: <fa368639-41f4-4e6d-8f43-0e5d774b9add@citrix.com>
On 04/11/2025 18:11, Andrew Cooper wrote:
> On 04/11/2025 4:12 pm, Tu Dinh wrote:
>> The LAML field should follow the TCG PFP specification:
>>
>> The TCG ACPI specification uses the field name "Log Area Minimum
>> Length", but the field value is the actual log area length reserved by
>> Platform Firmware, not a lower bound.
>>
>> Signed-off-by: Tu Dinh <ngoc-tu.dinh@vates.tech>
>> ---
>> tools/libacpi/build.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/tools/libacpi/build.c b/tools/libacpi/build.c
>> index 2f29863db1..95188e217e 100644
>> --- a/tools/libacpi/build.c
>> +++ b/tools/libacpi/build.c
>> @@ -473,7 +473,7 @@ static int construct_secondary_tables(struct acpi_ctxt *ctxt,
>> tpm2->platform_class = TPM2_ACPI_CLASS_CLIENT;
>> tpm2->control_area_address = TPM_CRB_CTRL_REQ;
>> tpm2->start_method = TPM2_START_METHOD_CRB;
>> - tpm2->log_area_minimum_length = TPM_LOG_AREA_MINIMUM_SIZE;
>> + tpm2->log_area_minimum_length = TPM_LOG_SIZE;
>
> These happen to be the same number, but in making this change
> TPM_LOG_AREA_MINIMUM_SIZE becomes unused.
>
> I suggest we delete the constant while at it. I don't think anything
> good can come from having two of them.
Agreed.
>
> Also, as it's no functional change, this is content for 4.22 I presume?
Yes, it's for 4.22.
>
> ~Andrew
>
--
Ngoc Tu Dinh | Vates XCP-ng Developer
XCP-ng & Xen Orchestra - Vates solutions
web: https://vates.tech
prev parent reply other threads:[~2025-11-05 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 16:12 [PATCH] acpi: Set TPM2 LAML to actual log area size Tu Dinh
2025-11-04 17:07 ` Andrew Cooper
2025-11-05 0:02 ` Tu Dinh [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=e6dbb09f-e7a3-40e1-83b4-0e0904dfbc1c@vates.tech \
--to=ngoc-tu.dinh@vates.tech \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=dpsmith@apertussolutions.com \
--cc=jbeulich@suse.com \
--cc=xen-devel@lists.xenproject.org \
/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).