From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Uri Lublin <uril@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [Qemu-commits] [COMMIT 95b134e] migrate.c: migrate_fd_put_buffer: Do not busyloop:stop writing if EWOULDBLOCK
Date: Wed, 20 May 2009 21:08:41 +0300 [thread overview]
Message-ID: <4A144729.9040606@redhat.com> (raw)
In-Reply-To: <200905201426.n4KEQ2gm008223@d03av02.boulder.ibm.com>
Anthony Liguori wrote:
> From: Uri Lublin <uril@redhat.com>
>
> The migration code is non-blocking, designed for live migration.
>
> Practically migrate_fd_put_buffer busy-loops trying to write, as
> on many machines EWOULDBLOCK==EAGAIN (look in include/asm-generic/errno.h).
>
>
stable?
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next parent reply other threads:[~2009-05-20 18:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200905201426.n4KEQ2gm008223@d03av02.boulder.ibm.com>
2009-05-20 18:08 ` Avi Kivity [this message]
2009-05-20 18:10 ` [Qemu-devel] Re: [Qemu-commits] [COMMIT 95b134e] migrate.c: migrate_fd_put_buffer: Do not busyloop:stop writing if EWOULDBLOCK Anthony Liguori
2009-05-20 18:22 ` Avi Kivity
2009-05-20 18:30 ` Anthony Liguori
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=4A144729.9040606@redhat.com \
--to=avi@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=uril@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 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).