qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Stefan Berger <stefanb@us.ibm.com>,
	qemu-devel@nongnu.org, Stefan Berger <stefanb@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2] Add ACPI tables for TPM
Date: Wed, 30 Jul 2014 18:24:37 +0200	[thread overview]
Message-ID: <53D91C45.5000700@redhat.com> (raw)
In-Reply-To: <20140730161129.GG27451@redhat.com>

On 07/30/14 18:11, Michael S. Tsirkin wrote:
> On Wed, Jul 30, 2014 at 06:07:28PM +0200, Laszlo Ersek wrote:
>> On 07/30/14 17:52, Michael S. Tsirkin wrote:

>>> How does EFI want to handle TCPA? Does caller allocate it
>>> log and fill in the address?
>>
>> TPM 1.2 seems to be completely absent from edk2, so I have no clue. TPM
>> 2.0 appears to be supported, but I already grepped edk2 for how it
>> handles the related ACPI table(s), and it doesn't. As far as I can see.
> 
> So it will basically just add it to RSDT and assume log pointer is
> filled in correctly by caller?

Yep.

Laszlo

  reply	other threads:[~2014-07-30 16:24 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
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 [this message]
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=53D91C45.5000700@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 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).