vhost-user-test: use g_cond_broadcast

g_cond_signal is rarely the right thing to do, it works now because
vhost-user-test only has two threads but it is not correct in general.
Fix it before adding more calls.

Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <1543851204-41186-7-git-send-email-pbonzini@redhat.com>
This commit is contained in:
Paolo Bonzini 2018-12-03 16:32:19 +01:00
parent 1c3d45df5e
commit 04ad1bf68e
1 changed files with 2 additions and 2 deletions

View File

@ -393,7 +393,7 @@ static void chr_read(void *opaque, const uint8_t *buf, int size)
G_N_ELEMENTS(s->fds));
/* signal the test that it can continue */
g_cond_signal(&s->data_cond);
g_cond_broadcast(&s->data_cond);
break;
case VHOST_USER_SET_VRING_KICK:
@ -419,7 +419,7 @@ static void chr_read(void *opaque, const uint8_t *buf, int size)
p = (uint8_t *) &msg;
qemu_chr_fe_write_all(chr, p, VHOST_USER_HDR_SIZE);
g_cond_signal(&s->data_cond);
g_cond_broadcast(&s->data_cond);
break;
case VHOST_USER_SET_VRING_BASE: