From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:33374) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDHVV-0003il-F9 for qemu-devel@nongnu.org; Mon, 10 Oct 2011 11:11:13 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RDHVP-00058w-N5 for qemu-devel@nongnu.org; Mon, 10 Oct 2011 11:11:09 -0400 Received: from mail-gy0-f173.google.com ([209.85.160.173]:56514) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RDHVP-00058f-Ee for qemu-devel@nongnu.org; Mon, 10 Oct 2011 11:11:03 -0400 Received: by gye5 with SMTP id 5so6839349gye.4 for ; Mon, 10 Oct 2011 08:11:02 -0700 (PDT) Message-ID: <4E930B02.30702@codemonkey.ws> Date: Mon, 10 Oct 2011 10:10:58 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <4E8B4826.8030500@redhat.com> <20111004222015.GB2926@amt.cnet> <4E930711.4020208@us.ibm.com> <4E93080A.6040603@redhat.com> In-Reply-To: <4E93080A.6040603@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1/1] kvm: support TSC deadline MSR List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: "Liu, Jinsong" , Marcelo Tosatti , qemu-devel@nongnu.org, kvm@vger.kernel.org On 10/10/2011 09:58 AM, Avi Kivity wrote: > On 10/10/2011 04:54 PM, Anthony Liguori wrote: >> On 10/04/2011 05:20 PM, Marcelo Tosatti wrote: >>> On Tue, Oct 04, 2011 at 07:53:42PM +0200, Avi Kivity wrote: >>>> On 10/03/2011 10:55 PM, Marcelo Tosatti wrote: >>>>> From: "Liu, Jinsong" >>>>> >>>>> KVM add emulation of lapic tsc deadline timer for guest. >>>>> This patch is co-operation work at qemu side. >>>>> >>>>> -#define CPU_SAVE_VERSION 12 >>>>> +#define CPU_SAVE_VERSION 13 >>>>> >>>>> >>>> >>>> Unfortunate. Can't we use subsections? >>> >>> Yes, i'll look into it tomorrow. >> >> Subsections are still broken at the moment although Juan has some patches. >> Bumping the version is the safe thing to do. >> > > It's irreversible, once we release a version with a bumped ID we can't go back. But the question is whether we've bumped *any* versions of common devices since 0.15 because if so, it's moot here. Once any device bumps a version id, migration is incompatible. Subsections are nice for stable branches, but they don't solve inter-version compatibility. Most importantly, subsections are broken today so until we straighten things out there, we can't rely on them. Regards, Anthony Liguori