From: Yaodong Yang <yyang@cse.unl.edu>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] QEMU live block-migration
Date: Mon, 8 Jul 2013 12:29:31 -0500 [thread overview]
Message-ID: <CAJ3ZQbO9_cinF1mVFqxeyTb5Yav66Qq1Dd0s=h_wU73Kc2hzHw@mail.gmail.com> (raw)
In-Reply-To: <20130708171836.32002.18544@loki>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
I used the qemu-kvm 1.2.0, so I did not find it in the code. I will move to
the current qemu version. Thanks!
On Mon, Jul 8, 2013 at 12:18 PM, Michael Roth <mdroth@linux.vnet.ibm.com>wrote:
> Quoting Yaodong Yang (2013-07-08 10:57:25)
> > Hello Michael,
> > Thanks for your help!
> > I read the function of tcp_wait_for_connect(), there is a statement; "
> > qemu_set_fd_handler2(s->fd, NULL, NULL, NULL, NULL); " I guess this
> will
> > disable this file-descriptor from the main loop and make the current
> > execution parallel with the main loop. Is it correct?
>
> Yup
>
> > Also, I did not find any thread_create related function in the
> > migrate_fd_connect() function.
>
> What version of QEMU are you looking at? For current releases you should
> see
> the following in migrate_fd_connect():
>
> qemu_thread_create(&s->thread, migration_thread, s,
> QEMU_THREAD_JOINABLE);
>
--
Yaodong Yang
Computer Science and Engineering Department
University of Nebraska--Lincoln,
Lincoln, NE, U.S.A.
[-- Attachment #2: Type: text/html, Size: 1576 bytes --]
next prev parent reply other threads:[~2013-07-08 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-07 14:55 [Qemu-devel] QEMU live block-migration Yaodong Yang
2013-07-08 15:32 ` Michael Roth
2013-07-08 15:57 ` Yaodong Yang
2013-07-08 17:18 ` Michael Roth
2013-07-08 17:29 ` Yaodong Yang [this message]
2013-07-08 18:02 ` Yaodong Yang
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='CAJ3ZQbO9_cinF1mVFqxeyTb5Yav66Qq1Dd0s=h_wU73Kc2hzHw@mail.gmail.com' \
--to=yyang@cse.unl.edu \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).