From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: guangrong.xiao@linux.intel.com, ehabkost@redhat.com,
mst@redhat.com, qemu-arm@nongnu.org, zhaoshenglong@huawei.com
Subject: [Qemu-devel] [PATCH v2 4/6] tpm: apci: cleanup TCPA table initialization
Date: Thu, 19 May 2016 15:19:28 +0200 [thread overview]
Message-ID: <1463663970-23661-5-git-send-email-imammedo@redhat.com> (raw)
In-Reply-To: <1463663970-23661-1-git-send-email-imammedo@redhat.com>
At the time build_tpm_tcpa() is called the tcpalog size is
always 0, so log_area_start_address which is actually offset
from the start of ACPI_BUILD_TPMLOG_FILE is always 0.
Also as 'TCPA' is allocated 0 filled, there is no point
in calculating always 0 log_area_start_address and set
tcpa->log_area_start_address to it since the field should
always point to start of ACPI_BUILD_TPMLOG_FILE.
Make code easier to read dropping not needed offset
calculations.
While at that move tcpalog allocation closer to the code
that defines its size.
Signed-off-by: Igor Mammedov <imammedo@redhat.com>
---
hw/i386/acpi-build.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git a/hw/i386/acpi-build.c b/hw/i386/acpi-build.c
index ce96533..c99dbe7 100644
--- a/hw/i386/acpi-build.c
+++ b/hw/i386/acpi-build.c
@@ -2391,11 +2391,10 @@ static void
build_tpm_tcpa(GArray *table_data, BIOSLinker *linker, GArray *tcpalog)
{
Acpi20Tcpa *tcpa = acpi_data_push(table_data, sizeof *tcpa);
- uint64_t log_area_start_address = acpi_data_len(tcpalog);
tcpa->platform_class = cpu_to_le16(TPM_TCPA_ACPI_CLASS_CLIENT);
tcpa->log_area_minimum_length = cpu_to_le32(TPM_LOG_AREA_MINIMUM_SIZE);
- tcpa->log_area_start_address = cpu_to_le64(log_area_start_address);
+ acpi_data_push(tcpalog, le32_to_cpu(tcpa->log_area_minimum_length));
bios_linker_loader_alloc(linker, ACPI_BUILD_TPMLOG_FILE, tcpalog, 1,
false /* high memory */);
@@ -2408,8 +2407,6 @@ build_tpm_tcpa(GArray *table_data, BIOSLinker *linker, GArray *tcpalog)
build_header(linker, table_data,
(void *)tcpa, "TCPA", sizeof(*tcpa), 2, NULL, NULL);
-
- acpi_data_push(tcpalog, TPM_LOG_AREA_MINIMUM_SIZE);
}
static void
--
1.8.3.1
next prev parent reply other threads:[~2016-05-19 13:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 13:19 [Qemu-devel] [PATCH v2 0/6] acpi: simplify bios_linker API Igor Mammedov
2016-05-19 13:19 ` [Qemu-devel] [PATCH v2 1/6] acpi: convert linker from GArray to BIOSLinker structure Igor Mammedov
2016-05-19 13:19 ` [Qemu-devel] [PATCH v2 2/6] acpi: simplify bios_linker API by removing redundant 'table' argument Igor Mammedov
2016-05-19 13:19 ` [Qemu-devel] [PATCH v2 3/6] acpi: cleanup bios_linker_loader_cleanup() Igor Mammedov
2016-05-19 13:19 ` Igor Mammedov [this message]
2016-05-19 13:19 ` [Qemu-devel] [PATCH v2 5/6] acpi: make bios_linker_loader_add_pointer() API offset based Igor Mammedov
2016-05-19 13:19 ` [Qemu-devel] [PATCH v2 6/6] acpi: make bios_linker_loader_add_checksum() " Igor Mammedov
2016-05-31 15:09 ` [Qemu-devel] [PATCH v2 0/6] acpi: simplify bios_linker API Igor Mammedov
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=1463663970-23661-5-git-send-email-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=ehabkost@redhat.com \
--cc=guangrong.xiao@linux.intel.com \
--cc=mst@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=zhaoshenglong@huawei.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).