From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: stefanb@linux.vnet.ibm.com, marcandre.lureau@redhat.com,
peter.maydell@linaro.org
Subject: [Qemu-devel] [PULL v2 0/6] Merge tpm 2018/01/26
Date: Mon, 29 Jan 2018 17:25:13 -0500 [thread overview]
Message-ID: <1517264719-18288-1-git-send-email-stefanb@linux.vnet.ibm.com> (raw)
The patches in this pull request fix a bug in the initialization of
a variable, adapt the cancel path used by the passthrough device to the
sysfs path of more recent versions of the Linux kernel, and do some other
cleanups preparing for support of migration. Finally, we add the CRB
interface emulation, which is used with a TPM 2.
The following changes since commit 0d1442912b3d6591a57ee45fbf28bc91e58d9e76:
Merge remote-tracking branch 'remotes/jasowang/tags/net-pull-request' into staging (2018-01-29 14:29:17 +0000)
are available in the git repository at:
git://github.com/stefanberger/qemu-tpm.git tags/pull-tpm-2018-01-26-2
for you to fetch changes up to 4ab6cb4c62273bb46102e5ae1d6af691b47cbcd8:
tpm: add CRB device (2018-01-29 14:22:50 -0500)
----------------------------------------------------------------
Merge tpm 2018/01/26 v2
----------------------------------------------------------------
Marc-André Lureau (5):
tpm: fix alignment issues
tpm: lookup cancel path under tpm device class
tpm: replace GThreadPool with AIO threadpool
tpm: report backend request error
tpm: add CRB device
Stefan Berger (1):
tpm: Set the flags of the CMD_INIT command to 0
backends/tpm.c | 59 +++++++++--------
default-configs/i386-softmmu.mak | 1 +
default-configs/x86_64-softmmu.mak | 1 +
hw/i386/acpi-build.c | 34 +++++++---
hw/tpm/Makefile.objs | 1 +
hw/tpm/tpm_crb.c | 303 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
hw/tpm/tpm_emulator.c | 39 +++++-------
hw/tpm/tpm_passthrough.c | 71 +++++++++++----------
hw/tpm/tpm_tis.c | 3 +-
hw/tpm/tpm_util.c | 75 ++++++++++------------
hw/tpm/tpm_util.h | 17 ++++-
include/hw/acpi/tpm.h | 51 +++++++++++++++
include/sysemu/tpm.h | 5 +-
include/sysemu/tpm_backend.h | 15 ++++-
qapi/tpm.json | 5 +-
tests/Makefile.include | 2 +
tests/tpm-crb-test.c | 275 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
17 files changed, 818 insertions(+), 139 deletions(-)
create mode 100644 hw/tpm/tpm_crb.c
create mode 100644 tests/tpm-crb-test.c
--
2.5.5
next reply other threads:[~2018-01-29 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 22:25 Stefan Berger [this message]
2018-01-29 22:25 ` [Qemu-devel] [PULL v2 1/6] tpm: Set the flags of the CMD_INIT command to 0 Stefan Berger
2018-02-26 22:47 ` Stefan Berger
2018-01-29 22:25 ` [Qemu-devel] [PULL v2 2/6] tpm: fix alignment issues Stefan Berger
2018-01-29 22:25 ` [Qemu-devel] [PULL v2 3/6] tpm: lookup cancel path under tpm device class Stefan Berger
2018-01-29 22:25 ` [Qemu-devel] [PULL v2 4/6] tpm: replace GThreadPool with AIO threadpool Stefan Berger
2018-01-29 22:25 ` [Qemu-devel] [PULL v2 5/6] tpm: report backend request error Stefan Berger
2018-01-29 22:25 ` [Qemu-devel] [PULL v2 6/6] tpm: add CRB device Stefan Berger
2018-01-30 16:53 ` [Qemu-devel] [PULL v2 0/6] Merge tpm 2018/01/26 Peter Maydell
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=1517264719-18288-1-git-send-email-stefanb@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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).