From: Stefan Berger <stefanb@linux.vnet.ibm.com>
To: stefanb@linux.vnet.ibm.com, qemu-devel@nongnu.org
Cc: andreas.niederl@iaik.tugraz.at
Subject: [Qemu-devel] [PATCH V2 6/9] Implement qemu_thread_join function
Date: Wed, 30 Mar 2011 15:42:17 -0400 [thread overview]
Message-ID: <20110330194237.957531180@linux.vnet.ibm.com> (raw)
In-Reply-To: 20110330194211.732385449@linux.vnet.ibm.com
[-- Attachment #1: qemu_thread_join.patch --]
[-- Type: text/plain, Size: 1401 bytes --]
This patch provides support for 'joining a thread' by wrapping the POSIX
pthread_join with qemu_thread_join.
Since the backend implementation is based on threads and I am stopping
and starting that thread during operations like 'snapshot resume', I
do use this functionality to synchronize with the TPM thread's termination
before terminating the TPM, creating a new one and loading previous state
from the time of the snapshot into the TPM.
Signed-off-by: Stefan Berger <stefanb@linux.vnet.ibm.com>
---
qemu-thread-posix.c | 5 +++++
qemu-thread.h | 1 +
2 files changed, 6 insertions(+)
Index: qemu-git/qemu-thread-posix.c
===================================================================
--- qemu-git.orig/qemu-thread-posix.c
+++ qemu-git/qemu-thread-posix.c
@@ -147,3 +147,8 @@ void qemu_thread_exit(void *retval)
{
pthread_exit(retval);
}
+
+int qemu_thread_join(QemuThread *thread, void **retval)
+{
+ return pthread_join(thread->thread, retval);
+}
Index: qemu-git/qemu-thread.h
===================================================================
--- qemu-git.orig/qemu-thread.h
+++ qemu-git/qemu-thread.h
@@ -35,5 +35,6 @@ void qemu_thread_create(QemuThread *thre
void qemu_thread_get_self(QemuThread *thread);
int qemu_thread_is_self(QemuThread *thread);
void qemu_thread_exit(void *retval);
+int qemu_thread_join(QemuThread *thread, void **retval);
#endif
next prev parent reply other threads:[~2011-03-30 19:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 19:42 [Qemu-devel] [PATCH V2 0/9] Qemu Trusted Platform Module (TPM) integration Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 1/9] Support for TPM command line options Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 2/9] Add TPM (frontend) hardware interface (TPM TIS) to Qemu Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 3/9] Add persistent state handling to TPM TIS frontend driver Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 4/9] Add tpm_tis driver to build process Stefan Berger
2011-04-01 18:14 ` Blue Swirl
2011-04-01 19:57 ` Stefan Berger
2011-04-03 9:20 ` Blue Swirl
2011-04-05 2:08 ` Stefan Berger
2011-04-05 17:45 ` Blue Swirl
2011-04-05 18:33 ` Stefan Berger
2011-04-05 18:55 ` Blue Swirl
2011-04-06 0:12 ` Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 5/9] Add a debug register Stefan Berger
2011-03-30 19:42 ` Stefan Berger [this message]
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 7/9] Add a TPM backend skeleton implementation Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 8/9] Implementation of the libtpms-based backend Stefan Berger
2011-03-30 19:42 ` [Qemu-devel] [PATCH V2 9/9] Add block storage support for libtpms based TPM backend 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=20110330194237.957531180@linux.vnet.ibm.com \
--to=stefanb@linux.vnet.ibm.com \
--cc=andreas.niederl@iaik.tugraz.at \
--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).