All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Umesh Deshpande <udeshpan@redhat.com>
Cc: kvm@vger.kernel.org, quintela@redhat.com, mtosatti@redhat.com,
	pbonzini@redhat.com
Subject: Re: [RFC PATCH v3 0/4] Separate thread for VM migration
Date: Thu, 11 Aug 2011 13:25:30 -0500	[thread overview]
Message-ID: <4E441E9A.4060300@codemonkey.ws> (raw)
In-Reply-To: <cover.1313076455.git.udeshpan@redhat.com>

On 08/11/2011 10:32 AM, Umesh Deshpande wrote:
> Following patch series 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.

This needs to go to qemu-devel.

Regards,

Anthony Liguori

>
> Umesh Deshpande (4):
>    separate thread for VM migration
>    synchronous migrate_cancel
>    lock to protect memslots
>    separate migration bitmap
>
>   arch_init.c         |   26 ++++++++++----
>   buffered_file.c     |  100 +++++++++++++++++++++++++++++++++------------------
>   buffered_file.h     |    4 ++
>   cpu-all.h           |   39 ++++++++++++++++++++
>   cpus.c              |   12 ++++++
>   exec.c              |   74 +++++++++++++++++++++++++++++++++++++
>   hw/hw.h             |    5 ++-
>   migration.c         |   50 ++++++++++++--------------
>   migration.h         |    6 +++
>   qemu-common.h       |    2 +
>   qemu-thread-posix.c |   10 +++++
>   qemu-thread.h       |    1 +
>   savevm.c            |   31 +++++++++++-----
>   13 files changed, 280 insertions(+), 80 deletions(-)
>


      parent reply	other threads:[~2011-08-11 18:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 15:32 [RFC PATCH v3 0/4] Separate thread for VM migration Umesh Deshpande
2011-08-11 15:32 ` [RFC PATCH v3 1/4] separate " Umesh Deshpande
2011-08-11 16:18   ` Paolo Bonzini
2011-08-11 17:36     ` Umesh Deshpande
2011-08-12  6:40       ` Paolo Bonzini
2011-08-11 15:32 ` [RFC PATCH v3 2/4] Making iothread block for migrate_cancel Umesh Deshpande
2011-08-11 15:32 ` [RFC PATCH v3 3/4] lock to protect memslots Umesh Deshpande
2011-08-11 16:20   ` Paolo Bonzini
2011-08-12  6:45     ` Paolo Bonzini
2011-08-15  6:45       ` Umesh Deshpande
2011-08-15 14:10         ` Paolo Bonzini
2011-08-15  7:26       ` Marcelo Tosatti
2011-08-15 14:14         ` Paolo Bonzini
2011-08-15 20:27           ` Umesh Deshpande
2011-08-16  6:15             ` Paolo Bonzini
2011-08-16  7:56               ` Paolo Bonzini
2011-08-11 15:32 ` [RFC PATCH v3 4/4] Separate migration bitmap Umesh Deshpande
2011-08-11 16:23 ` [RFC PATCH v3 0/4] Separate thread for VM migration Paolo Bonzini
2011-08-11 18:25 ` Anthony Liguori [this message]

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=4E441E9A.4060300@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --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.