From: Paolo Bonzini <pbonzini@redhat.com>
To: Umesh Deshpande <udeshpan@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org, quintela@redhat.com,
mtosatti@redhat.com
Subject: Re: [RFC PATCH v3 5/5] Making iothread block for migrate_cancel
Date: Wed, 17 Aug 2011 00:14:10 -0700 [thread overview]
Message-ID: <4E4B6A42.9020202@redhat.com> (raw)
In-Reply-To: <1f33d28d4f0c07905c8e1268e2071c05b9a6e53d.1313552764.git.udeshpan@redhat.com>
On 08/16/2011 08:56 PM, Umesh Deshpande wrote:
> diff --git a/qemu-thread-posix.c b/qemu-thread-posix.c
> index 2bd02ef..0d18b35 100644
> --- a/qemu-thread-posix.c
> +++ b/qemu-thread-posix.c
> @@ -115,6 +115,16 @@ void qemu_cond_wait(QemuCond *cond, QemuMutex *mutex)
> error_exit(err, __func__);
> }
>
> +void qemu_thread_join(QemuThread thread)
Should take a pointer.
Paolo
WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Umesh Deshpande <udeshpan@redhat.com>
Cc: mtosatti@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org,
quintela@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v3 5/5] Making iothread block for migrate_cancel
Date: Wed, 17 Aug 2011 00:14:10 -0700 [thread overview]
Message-ID: <4E4B6A42.9020202@redhat.com> (raw)
In-Reply-To: <1f33d28d4f0c07905c8e1268e2071c05b9a6e53d.1313552764.git.udeshpan@redhat.com>
On 08/16/2011 08:56 PM, Umesh Deshpande wrote:
> diff --git a/qemu-thread-posix.c b/qemu-thread-posix.c
> index 2bd02ef..0d18b35 100644
> --- a/qemu-thread-posix.c
> +++ b/qemu-thread-posix.c
> @@ -115,6 +115,16 @@ void qemu_cond_wait(QemuCond *cond, QemuMutex *mutex)
> error_exit(err, __func__);
> }
>
> +void qemu_thread_join(QemuThread thread)
Should take a pointer.
Paolo
next prev parent reply other threads:[~2011-08-17 7:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 3:56 [RFC PATCH v4 0/5] Separate thread for VM migration Umesh Deshpande
2011-08-17 3:56 ` [Qemu-devel] " Umesh Deshpande
2011-08-17 3:56 ` [RFC PATCH v4 1/5] MRU ram list Umesh Deshpande
2011-08-17 3:56 ` [Qemu-devel] " Umesh Deshpande
2011-08-17 3:56 ` [RFC PATCH v4 2/5] ramlist mutex Umesh Deshpande
2011-08-17 3:56 ` [Qemu-devel] " Umesh Deshpande
2011-08-17 6:28 ` Paolo Bonzini
2011-08-17 6:28 ` [Qemu-devel] " Paolo Bonzini
2011-08-19 6:20 ` Umesh Deshpande
2011-08-19 6:20 ` [Qemu-devel] " Umesh Deshpande
2011-08-22 6:48 ` Paolo Bonzini
2011-08-22 6:48 ` [Qemu-devel] " Paolo Bonzini
2011-08-23 9:15 ` Marcelo Tosatti
2011-08-23 9:15 ` [Qemu-devel] " Marcelo Tosatti
2011-08-23 9:17 ` Marcelo Tosatti
2011-08-23 9:17 ` [Qemu-devel] " Marcelo Tosatti
2011-08-23 11:41 ` Paolo Bonzini
2011-08-23 11:41 ` [Qemu-devel] " Paolo Bonzini
2011-08-23 12:16 ` Marcelo Tosatti
2011-08-23 12:16 ` [Qemu-devel] " Marcelo Tosatti
2011-08-17 3:56 ` [RFC PATCH v4 3/5] separate migration bitmap Umesh Deshpande
2011-08-17 3:56 ` [Qemu-devel] " Umesh Deshpande
2011-08-17 3:56 ` [RFC PATCH v4 4/5] separate thread for VM migration Umesh Deshpande
2011-08-17 3:56 ` [Qemu-devel] " Umesh Deshpande
2011-08-17 7:13 ` Paolo Bonzini
2011-08-17 7:13 ` [Qemu-devel] " Paolo Bonzini
2011-08-17 3:56 ` [RFC PATCH v3 5/5] Making iothread block for migrate_cancel Umesh Deshpande
2011-08-17 3:56 ` [Qemu-devel] " Umesh Deshpande
2011-08-17 7:14 ` Paolo Bonzini [this message]
2011-08-17 7:14 ` Paolo Bonzini
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=4E4B6A42.9020202@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=udeshpan@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.