From: Stefan Berger <stefanb@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, Stefan Berger <stefanb@linux.ibm.com>
Subject: [PULL v1 0/3] Merge tpm 2024/10/18 v1
Date: Fri, 18 Oct 2024 09:40:01 -0400 [thread overview]
Message-ID: <20241018134004.2110276-1-stefanb@linux.ibm.com> (raw)
Hello!
This PR fixes an issue with a TPM test case under heavy system load and
improves control channel error message handling.
Stefan
The following changes since commit 95a16ee753d6da651fce8df876333bf7fcf134d9:
Merge tag 'pull-loongarch-20241016' of https://gitlab.com/gaosong/qemu into staging (2024-10-17 12:42:23 +0100)
are available in the Git repository at:
https://github.com/stefanberger/qemu-tpm.git tags/pull-tpm-2024-10-18-1
for you to fetch changes up to d9280ea3174700170d39c4cdd3f587f260757711:
tests: Wait for migration completion on destination QEMU to avoid failures (2024-10-18 07:58:04 -0400)
Stefan Berger (3):
tpm: Use new ptm_cap_n structure for PTM_GET_CAPABILITY
tpm_emulator: Read control channel response in 2 passes
tests: Wait for migration completion on destination QEMU to avoid
failures
backends/tpm/tpm_emulator.c | 74 ++++++++++++++++++++++++++-----------
backends/tpm/tpm_ioctl.h | 13 ++++++-
backends/tpm/trace-events | 2 +-
tests/qtest/tpm-tests.c | 2 +-
4 files changed, 67 insertions(+), 24 deletions(-)
--
2.47.0
next reply other threads:[~2024-10-18 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 13:40 Stefan Berger [this message]
2024-10-18 13:40 ` [PULL v1 1/3] tpm: Use new ptm_cap_n structure for PTM_GET_CAPABILITY Stefan Berger
2024-10-18 13:40 ` [PULL v1 2/3] tpm_emulator: Read control channel response in 2 passes Stefan Berger
2024-10-18 13:40 ` [PULL v1 3/3] tests: Wait for migration completion on destination QEMU to avoid failures Stefan Berger
2024-10-21 11:36 ` [PULL v1 0/3] Merge tpm 2024/10/18 v1 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=20241018134004.2110276-1-stefanb@linux.ibm.com \
--to=stefanb@linux.ibm.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).