qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: lcapitulino@redhat.com
Subject: [Qemu-devel] [PATCH v2 0/2] Fix stop/cont vs. connect races
Date: Fri, 19 Oct 2012 16:45:22 +0200	[thread overview]
Message-ID: <1350657924-10624-1-git-send-email-pbonzini@redhat.com> (raw)

Here are two patches to make the handling more uniform when stop/cont
commands are sent to a QEMU instance that is waiting for incoming
migration.  Right now the handling will change, depending on whether
the command came before or after the source has connected.

The behavior that makes most sense is the one you have if the command
comes while migration is in progress and the monitor is blocked, so
ensure that we always resolve the race like that.

This will also help when incoming migration is moved to a coroutine,
which (by design) will cause the monitor not to block.

Paolo Bonzini (2):
  qmp: handle stop/cont in INMIGRATE state
  migration: go to paused state after finishing incoming migration with -S

 migration.c      |  2 +-
 qapi-schema.json |  7 +------
 qerror.h         |  3 ---
 qmp.c            | 17 +++++++++++------
 vl.c             |  2 +-
 5 file modificati, 14 inserzioni(+), 17 rimozioni(-)

-- 
1.7.12.1

             reply	other threads:[~2012-10-19 14:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 14:45 Paolo Bonzini [this message]
2012-10-19 14:45 ` [Qemu-devel] [PATCH v2 1/2] qmp: handle stop/cont in INMIGRATE state Paolo Bonzini
2012-10-22 15:06   ` Luiz Capitulino
2012-10-22 15:35     ` Paolo Bonzini
2012-10-22 15:38       ` Luiz Capitulino
2012-10-23 12:54         ` [Qemu-devel] [PATCH v3 " Paolo Bonzini
2012-10-23 13:39           ` Luiz Capitulino
2012-10-19 14:45 ` [Qemu-devel] [PATCH v2 2/2] migration: go to paused state after finishing incoming migration with -S 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=1350657924-10624-1-git-send-email-pbonzini@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=lcapitulino@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).