From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:36053) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TPDpj-0002jr-KM for qemu-devel@nongnu.org; Fri, 19 Oct 2012 10:46:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TPDpa-00044P-AH for qemu-devel@nongnu.org; Fri, 19 Oct 2012 10:45:55 -0400 Received: from mail-pb0-f45.google.com ([209.85.160.45]:64877) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TPDpZ-00043z-VB for qemu-devel@nongnu.org; Fri, 19 Oct 2012 10:45:46 -0400 Received: by mail-pb0-f45.google.com with SMTP id rp2so481441pbb.4 for ; Fri, 19 Oct 2012 07:45:45 -0700 (PDT) Sender: Paolo Bonzini From: Paolo Bonzini Date: Fri, 19 Oct 2012 16:45:22 +0200 Message-Id: <1350657924-10624-1-git-send-email-pbonzini@redhat.com> Subject: [Qemu-devel] [PATCH v2 0/2] Fix stop/cont vs. connect races List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: lcapitulino@redhat.com 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