xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Tu Dinh" <ngoc-tu.dinh@vates.tech>
To: "Jan Beulich" <jbeulich@suse.com>
Cc: "Anthony PERARD" <anthony.perard@vates.tech>,
	"Daniel Smith" <dpsmith@apertussolutions.com>,
	"Andrew Cooper" <andrew.cooper3@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH for-4.22 v2] acpi: Set TPM2 LAML to actual log area size
Date: Thu, 06 Nov 2025 12:23:57 +0000	[thread overview]
Message-ID: <a4a194b5-edab-47e2-9c95-5293e88f6d9b@vates.tech> (raw)
In-Reply-To: <e66a7724-12d3-42e2-805d-b32febb3d346@suse.com>

On 06/11/2025 13:19, Jan Beulich wrote:
> On 06.11.2025 13:13, Tu Dinh wrote:
>> On 06/11/2025 13:10, Jan Beulich wrote:
>>> On 05.11.2025 01:03, 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.
>>>
>>> And this is said where? Even the field description (ACPI 6.5) reads "Identifies
>>> the minimum length (in bytes) of the system’s preboot CC event log area." (I
>>> agree it makes little sense that way, but the change still needs proper
>>> explanation.)
>>
>> The above is an exact quote from the "TCG PC Client Platform Firmware
>> Profile Specification Version 1.06 Revision 52".
>
> Interesting. It didn't become clear to me that this actually is a quotation.
> Perhaps:
>
> The LAML field should follow the TCG PC Client Platform Firmware Profile
> Specification Version. Version 1.06 Revision 52 says:
>
> '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.'
>
> Remove the now-unused TPM_LOG_AREA_MINIMUM_SIZE.
>
> ? Then
> Acked-by: Jan Beulich <jbeulich@suse.com>
> and I could make the adjustment while committing (after 4.21 was branched off,
> of course).
>
> Jan

That's clearer, thanks.


--
Ngoc Tu Dinh | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech




      reply	other threads:[~2025-11-06 12:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05  0:03 [PATCH for-4.22 v2] acpi: Set TPM2 LAML to actual log area size Tu Dinh
2025-11-06 12:09 ` Jan Beulich
2025-11-06 12:13   ` Tu Dinh
2025-11-06 12:19     ` Jan Beulich
2025-11-06 12:23       ` 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=a4a194b5-edab-47e2-9c95-5293e88f6d9b@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).