From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: Stefan Berger <stefanb@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, amarnath.valluri@intel.com
Subject: Re: [Qemu-devel] [PATCH 0/5] tpm: Match frontend and backend buffer sizes (not 2.11)
Date: Wed, 8 Nov 2017 17:20:11 +0100 [thread overview]
Message-ID: <20171108162011.GB13150@boraha> (raw)
In-Reply-To: <1510016336-4086-1-git-send-email-stefanb@linux.vnet.ibm.com>
On Mon, Nov 06, 2017 at 07:58:51PM -0500, Stefan Berger wrote:
> This patch series does away with the hard coded buffer size in the TIS
> frontend and instead retrieves the buffer size from the device that's
> being used. So it gets it from the host device or the external emulator.
> In case the frontend (CRB) cannot support the backend's current buffer size
> (typically 4k) it can adjust the buffer size the emulator is working with
> so that we will not run into the problem that the backend produces packets
> that the frontend cannot deliver to due mismatching buffer sizes.
>
The approach looks ok to me. I don't have enough TPM/backend knowledge
to say how relevant that is in the long run. Modifying the CRB device
to set the buffer size to qemu CRB_CTRL_CMD_SIZE works. Windows 10 seems
happy at least.
Just a few remarks, I suppose you'll send a v2 soon,
thanks
> Stefan
>
> Stefan Berger (5):
> tpm: Move getting TPM buffer size to backends
> tpm: pull tpm_util_send() out of tpm_util_test()
> tpm: tpm_passthrough: Read the buffer size from the host device
> tpm: tpm_emulator: get and set buffer size of device
> tpm: tpm_passthrough: Fail startup if FE buffer size < BE buffer size
>
> backends/tpm.c | 13 +++-
> hw/tpm/tpm_emulator.c | 83 +++++++++++++++++++++++-
> hw/tpm/tpm_int.h | 9 +++
> hw/tpm/tpm_ioctl.h | 28 +++++++-
> hw/tpm/tpm_passthrough.c | 30 +++++++++
> hw/tpm/tpm_tis.c | 18 +++---
> hw/tpm/tpm_util.c | 149 +++++++++++++++++++++++++++++++++++++++++--
> hw/tpm/tpm_util.h | 3 +
> include/sysemu/tpm_backend.h | 17 ++++-
> 9 files changed, 327 insertions(+), 23 deletions(-)
>
> --
> 2.5.5
>
>
prev parent reply other threads:[~2017-11-08 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 0:58 [Qemu-devel] [PATCH 0/5] tpm: Match frontend and backend buffer sizes (not 2.11) Stefan Berger
2017-11-07 0:58 ` [Qemu-devel] [PATCH 1/5] tpm: Move getting TPM buffer size to backends Stefan Berger
2017-11-08 16:21 ` Marc-André Lureau
2017-11-08 18:19 ` Stefan Berger
2017-11-07 0:58 ` [Qemu-devel] [PATCH 2/5] tpm: pull tpm_util_send() out of tpm_util_test() Stefan Berger
2017-11-08 16:22 ` Marc-André Lureau
2017-11-07 0:58 ` [Qemu-devel] [PATCH 3/5] tpm: tpm_passthrough: Read the buffer size from the host device Stefan Berger
2017-11-07 12:28 ` Stefan Berger
2017-11-08 16:18 ` Marc-André Lureau
2017-11-07 0:58 ` [Qemu-devel] [PATCH 4/5] tpm: tpm_emulator: get and set buffer size of device Stefan Berger
2017-11-08 16:22 ` Marc-André Lureau
2017-11-08 17:50 ` Stefan Berger
2017-11-07 0:58 ` [Qemu-devel] [PATCH 5/5] tpm: tpm_passthrough: Fail startup if FE buffer size < BE buffer size Stefan Berger
2017-11-08 16:22 ` Marc-André Lureau
2017-11-08 18:20 ` Stefan Berger
2017-11-08 16:20 ` Marc-André Lureau [this message]
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=20171108162011.GB13150@boraha \
--to=marcandre.lureau@redhat.com \
--cc=amarnath.valluri@intel.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).