QEMUFileBuffered: indicate that we're ready when the underlying file is ready
commitcb03355a26a09bae91a8e5dea51538c9cccc838b
authorAvi Kivity <avi@redhat.com>
Wed, 7 Jul 2010 16:44:22 +0000 (7 19:44 +0300)
committerAnthony Liguori <aliguori@us.ibm.com>
Mon, 11 Oct 2010 23:20:52 +0000 (11 18:20 -0500)
treead55fcc05d58adc25fec44a2fd56b5b8bc58f62a
parentddfe317152193e70a996d9447d5bf2507d52c662
QEMUFileBuffered: indicate that we're ready when the underlying file is ready

QEMUFileBuffered stops writing when the underlying QEMUFile is not ready,
and tells its producer so.  However, when the underlying QEMUFile becomes
ready, it neglects to pass that information along, resulting in stoppage
of all data until the next tick (a tenths of a second).

Usually this doesn't matter, because most QEMUFiles used with QEMUFileBuffered
are almost always ready, but in the case of exec: migration this is not true,
due to the small pipe buffers used to connect to the target process.  The
result is very slow migration.

Fix by detecting the readiness notification and propagating it.  The detection
is a little ugly since QEMUFile overloads put_buffer() to send it, but that's
the suject for a different patch.

Signed-off-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
(cherry picked from commit 5e77aaa0d7d2f4ceaa4fcaf50f3a26d5150f34a6)
buffered_file.c