From: Laszlo Ersek <lersek@redhat.com>
To: Stefan Berger <stefanb@us.ibm.com>
Cc: Stefan Berger <stefanb@linux.vnet.ibm.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] Add ACPI tables for TPM
Date: Wed, 30 Jul 2014 19:18:53 +0200 [thread overview]
Message-ID: <53D928FD.8040805@redhat.com> (raw)
In-Reply-To: <OFC2A3D01E.3097CD90-ON85257D25.005AE3EE-85257D25.005B25F2@us.ibm.com>
On 07/30/14 18:35, Stefan Berger wrote:
> Laszlo Ersek <lersek@redhat.com> wrote on 07/30/2014 12:18:02 PM:
>
>> From: Laszlo Ersek <lersek@redhat.com>
>> To: "Michael S. Tsirkin" <mst@redhat.com>, Stefan Berger/Watson/IBM@IBMUS
>> Cc: qemu-devel@nongnu.org, Stefan Berger <stefanb@linux.vnet.ibm.com>
>> Date: 07/30/2014 12:18 PM
>> Subject: Re: [PATCH v2] Add ACPI tables for TPM
>>
>> On 07/30/14 18:10, Michael S. Tsirkin wrote:
>> > On Wed, Jul 30, 2014 at 12:03:46PM -0400, Stefan Berger wrote:
>> >> Laszlo Ersek <lersek@redhat.com> wrote on 07/30/2014 11:58:52 AM:
>>
>> >>> In the short term, probably skip TCPA, or advise users in
> documentation
>> >>> not to enable the TPM device when running OVMF.
>> >
>> > Hmm but doesn't OVMF rely on all tables being packed without holes
>> > in memory?
>> > I remember it did, and if it still does, this breaks unless TCPA is
>> > the last ...
>>
>> Ah, do you mean that the table size field in the ACPI table header of
>> TCPA would *not* include the TCG event log that is tacked-on? Yes, that
>> would certainly trip up the parser. It advances by looking at the table
>> size fields in the headers.
>
> Is this what finally requires another command for the linker/loader to
> allocate a chunk of memory where the size of the to-be-allocated memory
> is found
> at the location of the pointer ?
No, the above is a limitation of the current OVMF parser.
Thanks
Laszlo
next prev parent reply other threads:[~2014-07-30 17:19 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 10:52 [Qemu-devel] [PATCH v2] Add ACPI tables for TPM Stefan Berger
2014-07-30 11:17 ` Michael S. Tsirkin
2014-07-30 13:34 ` Stefan Berger
2014-07-30 13:20 ` Michael S. Tsirkin
2014-07-30 14:36 ` Laszlo Ersek
2014-07-30 14:46 ` Michael S. Tsirkin
2014-07-30 15:15 ` Laszlo Ersek
2014-07-30 15:37 ` Michael S. Tsirkin
2014-07-30 16:02 ` Laszlo Ersek
2014-07-30 16:07 ` Michael S. Tsirkin
2014-07-30 16:22 ` Laszlo Ersek
2014-07-30 15:03 ` Igor Mammedov
2014-07-30 15:29 ` Laszlo Ersek
2014-07-30 15:10 ` Stefan Berger
2014-07-30 15:20 ` Michael S. Tsirkin
2014-07-30 15:29 ` Stefan Berger
2014-07-30 15:41 ` Laszlo Ersek
2014-07-30 15:44 ` Stefan Berger
2014-07-30 15:58 ` Laszlo Ersek
2014-07-30 16:03 ` Stefan Berger
2014-07-30 16:10 ` Michael S. Tsirkin
2014-07-30 16:18 ` Laszlo Ersek
2014-07-30 16:35 ` Stefan Berger
2014-07-30 17:18 ` Laszlo Ersek [this message]
2014-07-30 15:50 ` Michael S. Tsirkin
2014-07-30 15:59 ` Stefan Berger
2014-07-30 16:05 ` Michael S. Tsirkin
2014-07-30 16:14 ` Laszlo Ersek
2014-07-30 16:19 ` Stefan Berger
2014-07-30 15:37 ` Laszlo Ersek
2014-07-30 15:52 ` Michael S. Tsirkin
2014-07-30 16:07 ` Laszlo Ersek
2014-07-30 16:11 ` Stefan Berger
2014-07-30 16:11 ` Michael S. Tsirkin
2014-07-30 16:24 ` Laszlo Ersek
2014-07-30 14:54 ` Stefan Berger
2014-07-30 15:07 ` Michael S. Tsirkin
2014-07-30 15:13 ` Stefan Berger
2014-07-30 15:25 ` Michael S. Tsirkin
2014-07-30 15:36 ` Stefan Berger
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=53D928FD.8040805@redhat.com \
--to=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanb@linux.vnet.ibm.com \
--cc=stefanb@us.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.