From: Stefan Berger <stefanb@linux.ibm.com>
To: Joelle van Dyne <j@getutm.app>, qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Ani Sinha <anisinha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [PATCH v5 05/14] tpm_crb: move ACPI table building to device interface
Date: Tue, 14 Nov 2023 11:44:08 -0500 [thread overview]
Message-ID: <20340277-648c-4ebd-825b-20199ceafe64@linux.ibm.com> (raw)
In-Reply-To: <865e5b38-0e83-4522-8d3e-410ba2394173@linux.ibm.com>
On 11/14/23 11:37, Stefan Berger wrote:
>
>
> On 11/13/23 21:09, Joelle van Dyne wrote:
>> This logic is similar to TPM TIS ISA device. Since TPM CRB can only
>> support TPM 2.0 backends, we check for this in realize.
>>
>> Signed-off-by: Joelle van Dyne <j@getutm.app>
>> ---
>> hw/tpm/tpm_crb.h | 2 ++
>> hw/i386/acpi-build.c | 16 +---------------
>> hw/tpm/tpm_crb.c | 16 ++++++++++++++++
>> hw/tpm/tpm_crb_common.c | 19 +++++++++++++++++++
>> 4 files changed, 38 insertions(+), 15 deletions(-)
>>
>> diff --git a/hw/tpm/tpm_crb.h b/hw/tpm/tpm_crb.h
>> index 36863e1664..e6a86e3fd1 100644
>> --- a/hw/tpm/tpm_crb.h
>> +++ b/hw/tpm/tpm_crb.h
>> @@ -73,5 +73,7 @@ void tpm_crb_init_memory(Object *obj, TPMCRBState
>> *s, Error **errp);
>> void tpm_crb_mem_save(TPMCRBState *s, uint32_t *saved_regs, void
>> *saved_cmdmem);
>> void tpm_crb_mem_load(TPMCRBState *s, const uint32_t *saved_regs,
>> const void *saved_cmdmem);
>> +void tpm_crb_build_aml(TPMIf *ti, Aml *scope, uint32_t baseaddr,
>> uint32_t size,
>> + bool build_ppi);
>>
>> #endif /* TPM_TPM_CRB_H */
>> diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
>> index 80db183b78..7491cee2af 100644
>> --- a/hw/i386/acpi-build.c
>> +++ b/hw/i386/acpi-build.c
>> @@ -1792,21 +1792,7 @@ build_dsdt(GArray *table_data, BIOSLinker *linker,
>>
>> #ifdef CONFIG_TPM
>> if (TPM_IS_CRB(tpm)) {
>> - dev = aml_device("TPM");
>> - aml_append(dev, aml_name_decl("_HID", aml_string("MSFT0101")));
>> - aml_append(dev, aml_name_decl("_STR",
>> - aml_string("TPM 2.0 Device")));
>> - crs = aml_resource_template();
>> - aml_append(crs, aml_memory32_fixed(TPM_CRB_ADDR_BASE,
>> - TPM_CRB_ADDR_SIZE,
>> AML_READ_WRITE));
>> - aml_append(dev, aml_name_decl("_CRS", crs));
>> -
>> - aml_append(dev, aml_name_decl("_STA", aml_int(0xf)));
>> - aml_append(dev, aml_name_decl("_UID", aml_int(1)));
>> -
>> - tpm_build_ppi_acpi(tpm, dev);
>> -
>> - aml_append(sb_scope, dev);
>> + call_dev_aml_func(DEVICE(tpm), scope);
>
> For an x86_64 VM we have to call it directly otherwise the ACPI table
> won't be there.
>
> tpm_crb_build_aml(tpm, sb_scope, TPM_CRB_ADDR_BASE,
> TPM_CRB_ADDR_SIZE, true);
>
>
I looks like a good place for the moved code would be in hw/acpi/tpm.c
next prev parent reply other threads:[~2023-11-14 16:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 2:09 [PATCH v5 00/14] tpm: introduce TPM CRB SysBus device Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 01/14] tpm_crb: refactor common code Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 02/14] tpm_crb: CTRL_RSP_ADDR is 64-bits wide Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 03/14] tpm_ppi: refactor memory space initialization Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 04/14] tpm_crb: use a single read-as-mem/write-as-mmio mapping Joelle van Dyne
2023-11-14 15:46 ` Stefan Berger
2023-11-14 2:09 ` [PATCH v5 05/14] tpm_crb: move ACPI table building to device interface Joelle van Dyne
2023-11-14 16:37 ` Stefan Berger
2023-11-14 16:44 ` Stefan Berger [this message]
2023-11-14 19:29 ` Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 06/14] tpm-sysbus: add plug handler for TPM on SysBus Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 07/14] hw/arm/virt: connect TPM to platform bus Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 08/14] hw/loongarch/virt: " Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 09/14] tpm_tis_sysbus: move DSDT AML generation to device Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 10/14] tests: acpi: prepare for TPM CRB tests Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 11/14] tpm_crb_sysbus: introduce TPM CRB SysBus device Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 12/14] tests: acpi: implement TPM CRB tests for ARM virt Joelle van Dyne
2023-11-14 9:36 ` Marc-André Lureau
2023-11-14 13:04 ` Stefan Berger
2023-11-14 18:03 ` Stefan Berger
2023-11-14 21:05 ` Stefan Berger
2023-11-15 0:12 ` Stefan Berger
2023-11-24 0:56 ` Joelle van Dyne
2023-11-24 16:17 ` Stefan Berger
2023-11-24 16:21 ` Joelle van Dyne
2023-11-24 16:26 ` Stefan Berger
2023-11-25 2:39 ` Joelle van Dyne
2023-11-27 14:12 ` Stefan Berger
2023-11-14 2:09 ` [PATCH v5 13/14] tests: acpi: updated expected blobs for TPM CRB Joelle van Dyne
2023-11-14 2:09 ` [PATCH v5 14/14] tests: add TPM-CRB sysbus tests for aarch64 Joelle van Dyne
2023-11-14 9:38 ` [PATCH v5 00/14] tpm: introduce TPM CRB SysBus device Marc-André Lureau
2023-11-14 19:25 ` Joelle van Dyne
2023-11-20 8:29 ` Marc-André Lureau
2023-11-20 15:01 ` Stefan Berger
2024-04-30 11:54 ` Peter Maydell
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=20340277-648c-4ebd-825b-20199ceafe64@linux.ibm.com \
--to=stefanb@linux.ibm.com \
--cc=anisinha@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=j@getutm.app \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).