From: Umesh Deshapnde <udeshpan@redhat.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Cc: Umesh Deshpande <udeshpan@redhat.com>
Subject: [RFC PATCH 0/2] A separate thread for VM migration
Date: Fri, 22 Jul 2011 15:58:14 -0400 [thread overview]
Message-ID: <cover.1311363171.git.udeshpan@redhat.com> (raw)
From: Umesh Deshpande <udeshpan@redhat.com>
Following patch deals with VCPU and iothread starvation during the migration of
a guest. Currently the iothread is responsible for performing the guest
migration. It holds qemu_mutex during the migration and doesn't allow VCPU to
enter the qemu mode and delays its return to the guest. The guest migration,
executed as an iohandler also delays the execution of other iohandlers. In the
following patch series, the migration has been moved to a separate thread to reduce the
qemu_mutex contention and iohandler starvation.
Umesh Deshpande (2):
new clock for migration routine
separate thread for VM migration
arch_init.c | 14 ++++++++++--
buffered_file.c | 12 ++++++----
exec.c | 4 +++
migration-tcp.c | 18 ++++++++--------
migration-unix.c | 7 ++---
migration.c | 59 ++++++++++++++++++++++++++++++-----------------------
migration.h | 4 +-
qemu-timer.c | 29 ++++++++++++++++++++++++-
qemu-timer.h | 3 ++
9 files changed, 99 insertions(+), 51 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-07-22 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 19:58 Umesh Deshapnde [this message]
2011-07-22 19:58 ` [RFC PATCH 1/2] new clock for migration routine Umesh Deshapnde
2011-07-22 19:58 ` [RFC PATCH 2/2] separate thread for VM migration Umesh Deshapnde
2011-07-26 11:13 ` 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=cover.1311363171.git.udeshpan@redhat.com \
--to=udeshpan@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@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