From: Laszlo Ersek <lersek@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: "Amarnath Valluri" <amarnath.valluri@intel.com>,
"qemu devel list" <qemu-devel@nongnu.org>,
"Daniel P. Berrange" <berrange@redhat.com>,
"Javier Martinez Canillas" <javierm@redhat.com>,
"Peter Jones" <pjones@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [Qemu-devel] TPM status
Date: Wed, 14 Jun 2017 15:51:33 +0200 [thread overview]
Message-ID: <7f0b8d00-236d-37e8-5c1f-e7ea8e4b9146@redhat.com> (raw)
Hi Stefan,
the MAINTAINERS file doesn't seem to cover any of the TPM-related files
in the tree:
backends/tpm.c
hw/tpm/
include/hw/acpi/tpm.h
include/sysemu/tpm*
tpm.c
but I have a gut feeling that you are semi-officially maintaining TPM
anyway, so I'm going to ask you. :)
Can you please write a document, to be placed under docs/specs/, that
describes the TPM device from a guest perspective, also explaining how
the guest-visible bits are connected to (current) TPM backend(s)?
The document wouldn't have to be very long; I think all standardized
interfaces could be mentioned by reference only (by spec names and
locations). The document should however describe any QEMU specifics, and
how the relevant specs are brought together in the implementation.
Some text files I'm familiar with and can recommend as examples:
- docs/specs/fw_cfg.txt
- docs/specs/pvpanic.txt
- docs/specs/vmgenid.txt
(There may be more and/or better examples of course.)
This document should be the starting point for developers that want to
support QEMU's TPM(s) in guest firmware that is different from SeaBIOS.
(You've been maintaining the related SeaBIOS feature.)
Would you be willing to author such a design document?
Thank you,
Laszlo
next reply other threads:[~2017-06-14 13:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 13:51 Laszlo Ersek [this message]
2017-06-14 15:00 ` [Qemu-devel] TPM status Stefan Berger
2017-06-27 16:12 ` Stefan Berger
2017-06-27 16:32 ` Laszlo Ersek
2017-06-29 19:31 ` Stefan Berger
2017-07-01 20:45 ` Laszlo Ersek
2017-06-28 15:22 ` Peter Jones
2017-06-28 16:44 ` Laszlo Ersek
2017-06-28 20:57 ` Stefan Berger
2017-06-28 21:26 ` Laszlo Ersek
2017-06-29 14:07 ` Javier Martinez Canillas
2017-06-29 16:59 ` Stefan Berger
2017-06-29 12:39 ` Javier Martinez Canillas
2017-06-29 16:09 ` Stefan Berger
2017-06-29 23:12 ` Javier Martinez Canillas
2017-06-30 0:55 ` 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=7f0b8d00-236d-37e8-5c1f-e7ea8e4b9146@redhat.com \
--to=lersek@redhat.com \
--cc=amarnath.valluri@intel.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=javierm@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pjones@redhat.com \
--cc=qemu-devel@nongnu.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).