From: Laszlo Ersek <lersek@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, javierm@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] specs: Describe the TPM support in QEMU
Date: Tue, 11 Jul 2017 21:36:28 +0200 [thread overview]
Message-ID: <e75d34d2-9fda-b514-3c22-655bb0c4b455@redhat.com> (raw)
In-Reply-To: <1499783493-15911-1-git-send-email-stefanb@linux.vnet.ibm.com>
On 07/11/17 16:31, Stefan Berger wrote:
> This patch adds a description of the current TPM support in QEMU
> to the specs.
>
> Several public specs are referenced via their landing page on the
> trustedcomputinggroup.org website.
>
> Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
>
> ---
>
> v1->v2:
> - fixed typos
> - added command line for starting an x86_64 VM with TPM passthrough device
> - added command lines for checks inside the VM
> ---
> docs/specs/tpm.txt | 124 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 124 insertions(+)
> create mode 100644 docs/specs/tpm.txt
Awesome, thank you very much!
I think I noticed one typo in new text:
> +#> dmesg | grep TCPA
> +[ 0.000000] ACPI: TCP 0x0000000003FFD191C 000032 (v02 BOCHS \
> + BXPCTCPA 0000001 BXPC 00000001)
I think the prefix here should be "ACPI: TCPA"; the letter "A" probably
fell victim to wrapping the line nicely.
Not sure which maintainer will pick up the patch, but I think they can
fix up this typo on their end (assuming no other reviewer asks for v3).
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
Thank you again, Stefan!
Laszlo
next prev parent reply other threads:[~2017-07-11 19:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-11 14:31 [Qemu-devel] [PATCH v2] specs: Describe the TPM support in QEMU Stefan Berger
2017-07-11 19:36 ` Laszlo Ersek [this message]
2017-07-11 20:48 ` Stefan Berger
2017-08-16 8:33 ` Javier Martinez Canillas
2017-08-16 9:03 ` Laszlo Ersek
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=e75d34d2-9fda-b514-3c22-655bb0c4b455@redhat.com \
--to=lersek@redhat.com \
--cc=javierm@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).