2011-03-12 17:43:52 +01:00
|
|
|
/*
|
|
|
|
* Win32 implementation for mutex/cond/thread functions
|
|
|
|
*
|
|
|
|
* Copyright Red Hat, Inc. 2010
|
|
|
|
*
|
|
|
|
* Author:
|
|
|
|
* Paolo Bonzini <pbonzini@redhat.com>
|
|
|
|
*
|
|
|
|
* This work is licensed under the terms of the GNU GPL, version 2 or later.
|
|
|
|
* See the COPYING file in the top-level directory.
|
|
|
|
*
|
|
|
|
*/
|
2017-03-24 23:01:41 +01:00
|
|
|
|
|
|
|
#ifndef _WIN32_WINNT
|
|
|
|
#define _WIN32_WINNT 0x0600
|
|
|
|
#endif
|
|
|
|
|
2016-01-29 18:49:55 +01:00
|
|
|
#include "qemu/osdep.h"
|
2011-03-12 17:43:52 +01:00
|
|
|
#include "qemu-common.h"
|
2012-12-17 18:20:00 +01:00
|
|
|
#include "qemu/thread.h"
|
2014-12-02 12:05:45 +01:00
|
|
|
#include "qemu/notify.h"
|
trace: add qemu mutex lock and unlock trace events
These trace events were very useful to help me to understand and find a
reordering issue in vfio, for example:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xa0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
that also helped me to see the desired result after the fix:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2000c, 4)
vfio_region_write (0001:03:00.0:region1+0xc4, 0xb0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
So it could be a good idea to have these traces implemented. It's worth
mentioning that they should be surgically enabled during the debugging,
otherwise it can flood the trace logs with lock/unlock messages.
How to use it:
trace-event qemu_mutex_lock on|off
trace-event qemu_mutex_unlock on|off
or
trace-event qemu_mutex* on|off
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
Message-Id: <1493054398-26013-1-git-send-email-joserz@linux.vnet.ibm.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
[Also handle trylock, cond_wait and win32; trace "unlocked" while still
in the critical section, so that "unlocked" always comes before the
next "locked" tracepoint. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-04-24 19:19:58 +02:00
|
|
|
#include "trace.h"
|
2011-03-12 17:43:52 +01:00
|
|
|
#include <process.h>
|
|
|
|
|
2014-01-30 11:20:31 +01:00
|
|
|
static bool name_threads;
|
|
|
|
|
|
|
|
void qemu_thread_naming(bool enable)
|
|
|
|
{
|
|
|
|
/* But note we don't actually name them on Windows yet */
|
|
|
|
name_threads = enable;
|
2014-03-12 12:48:18 +01:00
|
|
|
|
|
|
|
fprintf(stderr, "qemu: thread naming not supported on this host\n");
|
2014-01-30 11:20:31 +01:00
|
|
|
}
|
|
|
|
|
2011-03-12 17:43:52 +01:00
|
|
|
static void error_exit(int err, const char *msg)
|
|
|
|
{
|
|
|
|
char *pstr;
|
|
|
|
|
|
|
|
FormatMessage(FORMAT_MESSAGE_FROM_SYSTEM | FORMAT_MESSAGE_ALLOCATE_BUFFER,
|
|
|
|
NULL, err, 0, (LPTSTR)&pstr, 2, NULL);
|
|
|
|
fprintf(stderr, "qemu: %s: %s\n", msg, pstr);
|
|
|
|
LocalFree(pstr);
|
2011-09-21 09:28:31 +02:00
|
|
|
abort();
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_mutex_init(QemuMutex *mutex)
|
|
|
|
{
|
2017-03-24 23:01:41 +01:00
|
|
|
InitializeSRWLock(&mutex->lock);
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
2011-03-13 19:00:52 +01:00
|
|
|
void qemu_mutex_destroy(QemuMutex *mutex)
|
|
|
|
{
|
2017-03-24 23:01:41 +01:00
|
|
|
InitializeSRWLock(&mutex->lock);
|
2011-03-13 19:00:52 +01:00
|
|
|
}
|
|
|
|
|
2011-03-12 17:43:52 +01:00
|
|
|
void qemu_mutex_lock(QemuMutex *mutex)
|
|
|
|
{
|
2017-03-24 23:01:41 +01:00
|
|
|
AcquireSRWLockExclusive(&mutex->lock);
|
trace: add qemu mutex lock and unlock trace events
These trace events were very useful to help me to understand and find a
reordering issue in vfio, for example:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xa0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
that also helped me to see the desired result after the fix:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2000c, 4)
vfio_region_write (0001:03:00.0:region1+0xc4, 0xb0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
So it could be a good idea to have these traces implemented. It's worth
mentioning that they should be surgically enabled during the debugging,
otherwise it can flood the trace logs with lock/unlock messages.
How to use it:
trace-event qemu_mutex_lock on|off
trace-event qemu_mutex_unlock on|off
or
trace-event qemu_mutex* on|off
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
Message-Id: <1493054398-26013-1-git-send-email-joserz@linux.vnet.ibm.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
[Also handle trylock, cond_wait and win32; trace "unlocked" while still
in the critical section, so that "unlocked" always comes before the
next "locked" tracepoint. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-04-24 19:19:58 +02:00
|
|
|
trace_qemu_mutex_locked(mutex);
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
int qemu_mutex_trylock(QemuMutex *mutex)
|
|
|
|
{
|
|
|
|
int owned;
|
|
|
|
|
2017-03-24 23:01:41 +01:00
|
|
|
owned = TryAcquireSRWLockExclusive(&mutex->lock);
|
trace: add qemu mutex lock and unlock trace events
These trace events were very useful to help me to understand and find a
reordering issue in vfio, for example:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xa0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
that also helped me to see the desired result after the fix:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2000c, 4)
vfio_region_write (0001:03:00.0:region1+0xc4, 0xb0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
So it could be a good idea to have these traces implemented. It's worth
mentioning that they should be surgically enabled during the debugging,
otherwise it can flood the trace logs with lock/unlock messages.
How to use it:
trace-event qemu_mutex_lock on|off
trace-event qemu_mutex_unlock on|off
or
trace-event qemu_mutex* on|off
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
Message-Id: <1493054398-26013-1-git-send-email-joserz@linux.vnet.ibm.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
[Also handle trylock, cond_wait and win32; trace "unlocked" while still
in the critical section, so that "unlocked" always comes before the
next "locked" tracepoint. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-04-24 19:19:58 +02:00
|
|
|
if (owned) {
|
|
|
|
trace_qemu_mutex_locked(mutex);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
return -EBUSY;
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_mutex_unlock(QemuMutex *mutex)
|
|
|
|
{
|
trace: add qemu mutex lock and unlock trace events
These trace events were very useful to help me to understand and find a
reordering issue in vfio, for example:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xa0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
that also helped me to see the desired result after the fix:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2000c, 4)
vfio_region_write (0001:03:00.0:region1+0xc4, 0xb0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
So it could be a good idea to have these traces implemented. It's worth
mentioning that they should be surgically enabled during the debugging,
otherwise it can flood the trace logs with lock/unlock messages.
How to use it:
trace-event qemu_mutex_lock on|off
trace-event qemu_mutex_unlock on|off
or
trace-event qemu_mutex* on|off
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
Message-Id: <1493054398-26013-1-git-send-email-joserz@linux.vnet.ibm.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
[Also handle trylock, cond_wait and win32; trace "unlocked" while still
in the critical section, so that "unlocked" always comes before the
next "locked" tracepoint. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-04-24 19:19:58 +02:00
|
|
|
trace_qemu_mutex_unlocked(mutex);
|
2017-03-24 23:01:41 +01:00
|
|
|
ReleaseSRWLockExclusive(&mutex->lock);
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
2016-10-27 12:49:07 +02:00
|
|
|
void qemu_rec_mutex_init(QemuRecMutex *mutex)
|
|
|
|
{
|
|
|
|
InitializeCriticalSection(&mutex->lock);
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_rec_mutex_destroy(QemuRecMutex *mutex)
|
|
|
|
{
|
|
|
|
DeleteCriticalSection(&mutex->lock);
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_rec_mutex_lock(QemuRecMutex *mutex)
|
|
|
|
{
|
|
|
|
EnterCriticalSection(&mutex->lock);
|
|
|
|
}
|
|
|
|
|
|
|
|
int qemu_rec_mutex_trylock(QemuRecMutex *mutex)
|
|
|
|
{
|
|
|
|
return !TryEnterCriticalSection(&mutex->lock);
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_rec_mutex_unlock(QemuRecMutex *mutex)
|
|
|
|
{
|
|
|
|
LeaveCriticalSection(&mutex->lock);
|
|
|
|
}
|
|
|
|
|
2011-03-12 17:43:52 +01:00
|
|
|
void qemu_cond_init(QemuCond *cond)
|
|
|
|
{
|
|
|
|
memset(cond, 0, sizeof(*cond));
|
2017-03-24 23:01:41 +01:00
|
|
|
InitializeConditionVariable(&cond->var);
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
2011-03-13 19:00:52 +01:00
|
|
|
void qemu_cond_destroy(QemuCond *cond)
|
|
|
|
{
|
2017-03-24 23:01:41 +01:00
|
|
|
InitializeConditionVariable(&cond->var);
|
2011-03-13 19:00:52 +01:00
|
|
|
}
|
|
|
|
|
2011-03-12 17:43:52 +01:00
|
|
|
void qemu_cond_signal(QemuCond *cond)
|
|
|
|
{
|
2017-03-24 23:01:41 +01:00
|
|
|
WakeConditionVariable(&cond->var);
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_cond_broadcast(QemuCond *cond)
|
|
|
|
{
|
2017-03-24 23:01:41 +01:00
|
|
|
WakeAllConditionVariable(&cond->var);
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_cond_wait(QemuCond *cond, QemuMutex *mutex)
|
|
|
|
{
|
trace: add qemu mutex lock and unlock trace events
These trace events were very useful to help me to understand and find a
reordering issue in vfio, for example:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xa0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
that also helped me to see the desired result after the fix:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2000c, 4)
vfio_region_write (0001:03:00.0:region1+0xc4, 0xb0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
So it could be a good idea to have these traces implemented. It's worth
mentioning that they should be surgically enabled during the debugging,
otherwise it can flood the trace logs with lock/unlock messages.
How to use it:
trace-event qemu_mutex_lock on|off
trace-event qemu_mutex_unlock on|off
or
trace-event qemu_mutex* on|off
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
Message-Id: <1493054398-26013-1-git-send-email-joserz@linux.vnet.ibm.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
[Also handle trylock, cond_wait and win32; trace "unlocked" while still
in the critical section, so that "unlocked" always comes before the
next "locked" tracepoint. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-04-24 19:19:58 +02:00
|
|
|
trace_qemu_mutex_unlocked(mutex);
|
2017-03-24 23:01:41 +01:00
|
|
|
SleepConditionVariableSRW(&cond->var, &mutex->lock, INFINITE, 0);
|
trace: add qemu mutex lock and unlock trace events
These trace events were very useful to help me to understand and find a
reordering issue in vfio, for example:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2020c, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc4, 0xa0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
that also helped me to see the desired result after the fix:
qemu_mutex_lock locked mutex 0x10905ad8
vfio_region_write (0001:03:00.0:region1+0xc0, 0x2000c, 4)
vfio_region_write (0001:03:00.0:region1+0xc4, 0xb0000, 4)
qemu_mutex_unlock unlocked mutex 0x10905ad8
So it could be a good idea to have these traces implemented. It's worth
mentioning that they should be surgically enabled during the debugging,
otherwise it can flood the trace logs with lock/unlock messages.
How to use it:
trace-event qemu_mutex_lock on|off
trace-event qemu_mutex_unlock on|off
or
trace-event qemu_mutex* on|off
Signed-off-by: Jose Ricardo Ziviani <joserz@linux.vnet.ibm.com>
Message-Id: <1493054398-26013-1-git-send-email-joserz@linux.vnet.ibm.com>
Reviewed-by: Fam Zheng <famz@redhat.com>
[Also handle trylock, cond_wait and win32; trace "unlocked" while still
in the critical section, so that "unlocked" always comes before the
next "locked" tracepoint. - Paolo]
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
2017-04-24 19:19:58 +02:00
|
|
|
trace_qemu_mutex_locked(mutex);
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
2011-08-08 14:36:41 +02:00
|
|
|
void qemu_sem_init(QemuSemaphore *sem, int init)
|
|
|
|
{
|
|
|
|
/* Manual reset. */
|
|
|
|
sem->sema = CreateSemaphore(NULL, init, LONG_MAX, NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_sem_destroy(QemuSemaphore *sem)
|
|
|
|
{
|
|
|
|
CloseHandle(sem->sema);
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_sem_post(QemuSemaphore *sem)
|
|
|
|
{
|
|
|
|
ReleaseSemaphore(sem->sema, 1, NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
int qemu_sem_timedwait(QemuSemaphore *sem, int ms)
|
|
|
|
{
|
|
|
|
int rc = WaitForSingleObject(sem->sema, ms);
|
|
|
|
if (rc == WAIT_OBJECT_0) {
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
if (rc != WAIT_TIMEOUT) {
|
|
|
|
error_exit(GetLastError(), __func__);
|
|
|
|
}
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_sem_wait(QemuSemaphore *sem)
|
|
|
|
{
|
|
|
|
if (WaitForSingleObject(sem->sema, INFINITE) != WAIT_OBJECT_0) {
|
|
|
|
error_exit(GetLastError(), __func__);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-08-12 15:38:18 +02:00
|
|
|
/* Wrap a Win32 manual-reset event with a fast userspace path. The idea
|
|
|
|
* is to reset the Win32 event lazily, as part of a test-reset-test-wait
|
|
|
|
* sequence. Such a sequence is, indeed, how QemuEvents are used by
|
|
|
|
* RCU and other subsystems!
|
|
|
|
*
|
|
|
|
* Valid transitions:
|
|
|
|
* - free->set, when setting the event
|
2017-01-12 19:07:54 +01:00
|
|
|
* - busy->set, when setting the event, followed by SetEvent
|
2015-08-12 15:38:18 +02:00
|
|
|
* - set->free, when resetting the event
|
|
|
|
* - free->busy, when waiting
|
|
|
|
*
|
|
|
|
* set->busy does not happen (it can be observed from the outside but
|
|
|
|
* it really is set->free->busy).
|
|
|
|
*
|
|
|
|
* busy->free provably cannot happen; to enforce it, the set->free transition
|
|
|
|
* is done with an OR, which becomes a no-op if the event has concurrently
|
|
|
|
* transitioned to free or busy (and is faster than cmpxchg).
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define EV_SET 0
|
|
|
|
#define EV_FREE 1
|
|
|
|
#define EV_BUSY -1
|
|
|
|
|
2013-09-25 08:20:59 +02:00
|
|
|
void qemu_event_init(QemuEvent *ev, bool init)
|
|
|
|
{
|
|
|
|
/* Manual reset. */
|
2015-08-12 15:38:18 +02:00
|
|
|
ev->event = CreateEvent(NULL, TRUE, TRUE, NULL);
|
|
|
|
ev->value = (init ? EV_SET : EV_FREE);
|
2013-09-25 08:20:59 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_event_destroy(QemuEvent *ev)
|
|
|
|
{
|
|
|
|
CloseHandle(ev->event);
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_event_set(QemuEvent *ev)
|
|
|
|
{
|
2016-09-19 11:10:57 +02:00
|
|
|
/* qemu_event_set has release semantics, but because it *loads*
|
|
|
|
* ev->value we need a full memory barrier here.
|
|
|
|
*/
|
|
|
|
smp_mb();
|
|
|
|
if (atomic_read(&ev->value) != EV_SET) {
|
2015-08-12 15:38:18 +02:00
|
|
|
if (atomic_xchg(&ev->value, EV_SET) == EV_BUSY) {
|
|
|
|
/* There were waiters, wake them up. */
|
|
|
|
SetEvent(ev->event);
|
|
|
|
}
|
|
|
|
}
|
2013-09-25 08:20:59 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_event_reset(QemuEvent *ev)
|
|
|
|
{
|
2016-09-19 11:10:57 +02:00
|
|
|
unsigned value;
|
|
|
|
|
|
|
|
value = atomic_read(&ev->value);
|
|
|
|
smp_mb_acquire();
|
|
|
|
if (value == EV_SET) {
|
2015-08-12 15:38:18 +02:00
|
|
|
/* If there was a concurrent reset (or even reset+wait),
|
|
|
|
* do nothing. Otherwise change EV_SET->EV_FREE.
|
|
|
|
*/
|
|
|
|
atomic_or(&ev->value, EV_FREE);
|
|
|
|
}
|
2013-09-25 08:20:59 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_event_wait(QemuEvent *ev)
|
|
|
|
{
|
2015-08-12 15:38:18 +02:00
|
|
|
unsigned value;
|
|
|
|
|
2016-09-19 11:10:57 +02:00
|
|
|
value = atomic_read(&ev->value);
|
|
|
|
smp_mb_acquire();
|
2015-08-12 15:38:18 +02:00
|
|
|
if (value != EV_SET) {
|
|
|
|
if (value == EV_FREE) {
|
|
|
|
/* qemu_event_set is not yet going to call SetEvent, but we are
|
|
|
|
* going to do another check for EV_SET below when setting EV_BUSY.
|
|
|
|
* At that point it is safe to call WaitForSingleObject.
|
|
|
|
*/
|
|
|
|
ResetEvent(ev->event);
|
|
|
|
|
|
|
|
/* Tell qemu_event_set that there are waiters. No need to retry
|
|
|
|
* because there cannot be a concurent busy->free transition.
|
|
|
|
* After the CAS, the event will be either set or busy.
|
|
|
|
*/
|
|
|
|
if (atomic_cmpxchg(&ev->value, EV_FREE, EV_BUSY) == EV_SET) {
|
|
|
|
value = EV_SET;
|
|
|
|
} else {
|
|
|
|
value = EV_BUSY;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
if (value == EV_BUSY) {
|
|
|
|
WaitForSingleObject(ev->event, INFINITE);
|
|
|
|
}
|
|
|
|
}
|
2013-09-25 08:20:59 +02:00
|
|
|
}
|
|
|
|
|
2011-03-12 17:43:52 +01:00
|
|
|
struct QemuThreadData {
|
2011-12-12 17:21:33 +01:00
|
|
|
/* Passed to win32_start_routine. */
|
|
|
|
void *(*start_routine)(void *);
|
|
|
|
void *arg;
|
|
|
|
short mode;
|
2014-12-02 12:05:45 +01:00
|
|
|
NotifierList exit;
|
2011-12-12 17:21:33 +01:00
|
|
|
|
|
|
|
/* Only used for joinable threads. */
|
|
|
|
bool exited;
|
|
|
|
void *ret;
|
|
|
|
CRITICAL_SECTION cs;
|
2011-03-12 17:43:52 +01:00
|
|
|
};
|
|
|
|
|
2014-12-02 12:05:45 +01:00
|
|
|
static bool atexit_registered;
|
|
|
|
static NotifierList main_thread_exit;
|
|
|
|
|
2012-11-23 12:12:01 +01:00
|
|
|
static __thread QemuThreadData *qemu_thread_data;
|
2011-03-12 17:43:52 +01:00
|
|
|
|
2014-12-02 12:05:45 +01:00
|
|
|
static void run_main_thread_exit(void)
|
|
|
|
{
|
|
|
|
notifier_list_notify(&main_thread_exit, NULL);
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_thread_atexit_add(Notifier *notifier)
|
|
|
|
{
|
|
|
|
if (!qemu_thread_data) {
|
|
|
|
if (!atexit_registered) {
|
|
|
|
atexit_registered = true;
|
|
|
|
atexit(run_main_thread_exit);
|
|
|
|
}
|
|
|
|
notifier_list_add(&main_thread_exit, notifier);
|
|
|
|
} else {
|
|
|
|
notifier_list_add(&qemu_thread_data->exit, notifier);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_thread_atexit_remove(Notifier *notifier)
|
|
|
|
{
|
|
|
|
notifier_remove(notifier);
|
|
|
|
}
|
|
|
|
|
2011-03-12 17:43:52 +01:00
|
|
|
static unsigned __stdcall win32_start_routine(void *arg)
|
|
|
|
{
|
2011-12-12 17:21:33 +01:00
|
|
|
QemuThreadData *data = (QemuThreadData *) arg;
|
|
|
|
void *(*start_routine)(void *) = data->start_routine;
|
|
|
|
void *thread_arg = data->arg;
|
|
|
|
|
2012-11-23 12:12:01 +01:00
|
|
|
qemu_thread_data = data;
|
2011-12-12 17:21:33 +01:00
|
|
|
qemu_thread_exit(start_routine(thread_arg));
|
2011-03-12 17:43:52 +01:00
|
|
|
abort();
|
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_thread_exit(void *arg)
|
|
|
|
{
|
2012-11-23 12:12:01 +01:00
|
|
|
QemuThreadData *data = qemu_thread_data;
|
|
|
|
|
2014-12-02 12:05:45 +01:00
|
|
|
notifier_list_notify(&data->exit, NULL);
|
|
|
|
if (data->mode == QEMU_THREAD_JOINABLE) {
|
2011-12-12 17:21:33 +01:00
|
|
|
data->ret = arg;
|
|
|
|
EnterCriticalSection(&data->cs);
|
|
|
|
data->exited = true;
|
|
|
|
LeaveCriticalSection(&data->cs);
|
2014-12-02 12:05:45 +01:00
|
|
|
} else {
|
|
|
|
g_free(data);
|
2011-12-12 17:21:33 +01:00
|
|
|
}
|
|
|
|
_endthreadex(0);
|
|
|
|
}
|
|
|
|
|
|
|
|
void *qemu_thread_join(QemuThread *thread)
|
|
|
|
{
|
|
|
|
QemuThreadData *data;
|
|
|
|
void *ret;
|
|
|
|
HANDLE handle;
|
|
|
|
|
|
|
|
data = thread->data;
|
2014-12-02 12:05:45 +01:00
|
|
|
if (data->mode == QEMU_THREAD_DETACHED) {
|
2011-12-12 17:21:33 +01:00
|
|
|
return NULL;
|
|
|
|
}
|
2014-12-02 12:05:45 +01:00
|
|
|
|
2011-12-12 17:21:33 +01:00
|
|
|
/*
|
|
|
|
* Because multiple copies of the QemuThread can exist via
|
|
|
|
* qemu_thread_get_self, we need to store a value that cannot
|
|
|
|
* leak there. The simplest, non racy way is to store the TID,
|
|
|
|
* discard the handle that _beginthreadex gives back, and
|
|
|
|
* get another copy of the handle here.
|
|
|
|
*/
|
2011-12-13 13:43:52 +01:00
|
|
|
handle = qemu_thread_get_handle(thread);
|
|
|
|
if (handle) {
|
2011-12-12 17:21:33 +01:00
|
|
|
WaitForSingleObject(handle, INFINITE);
|
|
|
|
CloseHandle(handle);
|
|
|
|
}
|
|
|
|
ret = data->ret;
|
|
|
|
DeleteCriticalSection(&data->cs);
|
|
|
|
g_free(data);
|
|
|
|
return ret;
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
2014-01-30 11:20:32 +01:00
|
|
|
void qemu_thread_create(QemuThread *thread, const char *name,
|
2011-03-12 17:43:52 +01:00
|
|
|
void *(*start_routine)(void *),
|
2011-12-12 17:21:31 +01:00
|
|
|
void *arg, int mode)
|
2011-03-12 17:43:52 +01:00
|
|
|
{
|
|
|
|
HANDLE hThread;
|
|
|
|
struct QemuThreadData *data;
|
2012-11-23 12:12:01 +01:00
|
|
|
|
2011-08-21 05:09:37 +02:00
|
|
|
data = g_malloc(sizeof *data);
|
2011-03-12 17:43:52 +01:00
|
|
|
data->start_routine = start_routine;
|
|
|
|
data->arg = arg;
|
2011-12-12 17:21:33 +01:00
|
|
|
data->mode = mode;
|
|
|
|
data->exited = false;
|
2014-12-02 12:05:45 +01:00
|
|
|
notifier_list_init(&data->exit);
|
2011-03-12 17:43:52 +01:00
|
|
|
|
2012-01-31 07:14:15 +01:00
|
|
|
if (data->mode != QEMU_THREAD_DETACHED) {
|
|
|
|
InitializeCriticalSection(&data->cs);
|
|
|
|
}
|
|
|
|
|
2011-03-12 17:43:52 +01:00
|
|
|
hThread = (HANDLE) _beginthreadex(NULL, 0, win32_start_routine,
|
2011-12-12 17:21:33 +01:00
|
|
|
data, 0, &thread->tid);
|
2011-03-12 17:43:52 +01:00
|
|
|
if (!hThread) {
|
|
|
|
error_exit(GetLastError(), __func__);
|
|
|
|
}
|
|
|
|
CloseHandle(hThread);
|
2014-12-02 12:05:45 +01:00
|
|
|
thread->data = data;
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
void qemu_thread_get_self(QemuThread *thread)
|
|
|
|
{
|
2012-11-23 12:12:01 +01:00
|
|
|
thread->data = qemu_thread_data;
|
2011-12-12 17:21:33 +01:00
|
|
|
thread->tid = GetCurrentThreadId();
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|
|
|
|
|
2011-12-13 13:43:52 +01:00
|
|
|
HANDLE qemu_thread_get_handle(QemuThread *thread)
|
|
|
|
{
|
|
|
|
QemuThreadData *data;
|
|
|
|
HANDLE handle;
|
|
|
|
|
|
|
|
data = thread->data;
|
2014-12-02 12:05:45 +01:00
|
|
|
if (data->mode == QEMU_THREAD_DETACHED) {
|
2011-12-13 13:43:52 +01:00
|
|
|
return NULL;
|
|
|
|
}
|
|
|
|
|
|
|
|
EnterCriticalSection(&data->cs);
|
|
|
|
if (!data->exited) {
|
2017-01-10 11:59:57 +01:00
|
|
|
handle = OpenThread(SYNCHRONIZE | THREAD_SUSPEND_RESUME |
|
|
|
|
THREAD_SET_CONTEXT, FALSE, thread->tid);
|
2011-12-13 13:43:52 +01:00
|
|
|
} else {
|
|
|
|
handle = NULL;
|
|
|
|
}
|
|
|
|
LeaveCriticalSection(&data->cs);
|
|
|
|
return handle;
|
|
|
|
}
|
|
|
|
|
2012-05-02 17:21:31 +02:00
|
|
|
bool qemu_thread_is_self(QemuThread *thread)
|
2011-03-12 17:43:52 +01:00
|
|
|
{
|
2011-12-12 17:21:33 +01:00
|
|
|
return GetCurrentThreadId() == thread->tid;
|
2011-03-12 17:43:52 +01:00
|
|
|
}
|