Message ID | 20190602034239.23225-1-chen.zhang@intel.com (mailing list archive) |
---|---|
Headers | show
Return-Path: <qemu-devel-bounces+patchwork-qemu-devel=patchwork.kernel.org@nongnu.org> Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork-2.web.codeaurora.org (Postfix) with ESMTP id 17ADE1515 for <patchwork-qemu-devel@patchwork.kernel.org>; Sun, 2 Jun 2019 03:48:34 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id F41A628B83 for <patchwork-qemu-devel@patchwork.kernel.org>; Sun, 2 Jun 2019 03:48:33 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id E5E5D28B82; Sun, 2 Jun 2019 03:48:33 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.2 required=2.0 tests=BAYES_00,FROM_ADDR_WS, FROM_WSP_TRAIL,MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id C035E28B82 for <patchwork-qemu-devel@patchwork.kernel.org>; Sun, 2 Jun 2019 03:48:32 +0000 (UTC) Received: from localhost ([127.0.0.1]:44452 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <qemu-devel-bounces+patchwork-qemu-devel=patchwork.kernel.org@nongnu.org>) id 1hXHU0-00085Y-2T for patchwork-qemu-devel@patchwork.kernel.org; Sat, 01 Jun 2019 23:48:32 -0400 Received: from eggs.gnu.org ([209.51.188.92]:47038) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from <chen.zhang@intel.com>) id 1hXHSo-0007Dv-Qq for qemu-devel@nongnu.org; Sat, 01 Jun 2019 23:47:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from <chen.zhang@intel.com>) id 1hXHSn-00039Z-QR for qemu-devel@nongnu.org; Sat, 01 Jun 2019 23:47:18 -0400 Received: from mga12.intel.com ([192.55.52.136]:51833) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from <chen.zhang@intel.com>) id 1hXHSn-00030z-Hz for qemu-devel@nongnu.org; Sat, 01 Jun 2019 23:47:17 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jun 2019 20:47:09 -0700 X-ExtLoop1: 1 Received: from unknown (HELO localhost.localdomain) ([10.239.13.19]) by orsmga005.jf.intel.com with ESMTP; 01 Jun 2019 20:47:07 -0700 From: Zhang Chen <chen.zhang@intel.com > To: Li Zhijian <lizhijian@cn.fujitsu.com>, "Dr. David Alan Gilbert" <dgilbert@redhat.com>, Juan Quintela <quintela@redhat.com>, zhanghailiang <zhang.zhanghailiang@huawei.com>, Jason Wang <jasowang@redhat.com>, qemu-dev <qemu-devel@nongnu.org> Date: Sun, 2 Jun 2019 11:42:33 +0800 Message-Id: <20190602034239.23225-1-chen.zhang@intel.com> X-Mailer: git-send-email 2.17.GIT X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 192.55.52.136 Subject: [Qemu-devel] [PATCH 0/6] Add Xen COLO support X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: <qemu-devel.nongnu.org> List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>, <mailto:qemu-devel-request@nongnu.org?subject=unsubscribe> List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel/> List-Post: <mailto:qemu-devel@nongnu.org> List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help> List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>, <mailto:qemu-devel-request@nongnu.org?subject=subscribe> Cc: Zhang Chen <chen.zhang@intel.com>, Zhang Chen <zhangckid@gmail.com> Errors-To: qemu-devel-bounces+patchwork-qemu-devel=patchwork.kernel.org@nongnu.org Sender: "Qemu-devel" <qemu-devel-bounces+patchwork-qemu-devel=patchwork.kernel.org@nongnu.org> X-Virus-Scanned: ClamAV using ClamSMTP |
Series |
Add Xen COLO support
|
expand
|
From: Zhang Chen <chen.zhang@intel.com> Xen COLO based on KVM COLO architecture, it shared COLO proxy and block replication with KVM COLO. The only differece is Xen COLO have own COLO-frame to handle live migration related function, so we need this series make Xen COLO frame can communicate with other COLO modules in qemu. Xen side related patches have been merged. Zhang Chen (6): COLO-compare: Add new parameter to communicate with remote colo-frame COLO-compare: Add remote notification chardev handler frame COLO-compare: Make the compare_chr_send() can send notification message. COLO-compare: Add colo-compare remote notify support COLO-compare: Rename the colo_compare_inconsistency_notify migration/colo.c: Add missed filter notify for Xen COLO. migration/colo.c | 2 + net/colo-compare.c | 154 ++++++++++++++++++++++++++++++++++++++++----- qemu-options.hx | 33 +++++++++- 3 files changed, 174 insertions(+), 15 deletions(-)