From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:49670) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xc2Aj-0001Cc-8W for qemu-devel@nongnu.org; Wed, 08 Oct 2014 21:05:41 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xc2Ad-0000Xu-Q9 for qemu-devel@nongnu.org; Wed, 08 Oct 2014 21:05:36 -0400 Received: from [59.151.112.132] (port=29741 helo=heian.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xc2Ac-0000X5-QG for qemu-devel@nongnu.org; Wed, 08 Oct 2014 21:05:31 -0400 Message-ID: <5435DF95.5080800@cn.fujitsu.com> Date: Thu, 9 Oct 2014 09:06:29 +0800 From: Wen Congyang MIME-Version: 1.0 References: <1411464235-5653-1-git-send-email-yanghy@cn.fujitsu.com> <1411464235-5653-4-git-send-email-yanghy@cn.fujitsu.com> <54355209.2050304@redhat.com> In-Reply-To: <54355209.2050304@redhat.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RFC PATCH v2 03/23] COLO: introduce an api colo_supported() to indicate COLO support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake , Yang Hongyang , qemu-devel@nongnu.org Cc: GuiJianfeng@cn.fujitsu.com, yunhong.jiang@intel.com, eddie.dong@intel.com, dgilbert@redhat.com, mrhines@linux.vnet.ibm.com On 10/08/2014 11:02 PM, Eric Blake wrote: > On 09/23/2014 03:23 AM, Yang Hongyang wrote: >> introduce an api colo_supported() to indicate COLO support, returns >> true if colo supported (configured with --enable-colo). >> >> Signed-off-by: Yang Hongyang >> --- > >> +++ b/include/migration/migration-colo.h >> @@ -0,0 +1,18 @@ >> +/* >> + * COarse-grain LOck-stepping Virtual Machines for Non-stop Service (COLO) >> + * (a.k.a. Fault Tolerance or Continuous Replication) >> + * >> + * Copyright (C) 2014 FUJITSU LIMITED >> + * >> + * This work is licensed under the terms of the GNU GPL, version 2. See >> + * the COPYING file in the top-level directory. > > Is there any reason you are forbidding the use of this file in a GPLv3 > project? We prefer new files to be GPLv2+, not GPLv2-only (by the use > of the "or later" clause), unless there is strong reason why it is not > possible. I don't know the reason, and I think it is OK to be GPLv2+ Thanks Wen Congyang > > >> +++ b/migration-colo.c >> @@ -0,0 +1,16 @@ >> +/* >> + * COarse-grain LOck-stepping Virtual Machines for Non-stop Service (COLO) >> + * (a.k.a. Fault Tolerance or Continuous Replication) >> + * >> + * Copyright (C) 2014 FUJITSU LIMITED >> + * >> + * This work is licensed under the terms of the GNU GPL, version 2. See >> + * the COPYING file in the top-level directory. > > Same comment for all new files. >