All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@redhat.com>
Cc: "Liu, Jinsong" <jinsong.liu@intel.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 1/1] kvm: support TSC deadline MSR
Date: Mon, 10 Oct 2011 10:10:58 -0500	[thread overview]
Message-ID: <4E930B02.30702@codemonkey.ws> (raw)
In-Reply-To: <4E93080A.6040603@redhat.com>

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"<jinsong.liu@intel.com>
>>>>>
>>>>> 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


  reply	other threads:[~2011-10-10 15:11 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-03 20:55 [PATCH 0/1] [PULL] qemu-kvm.git uq/master queue Marcelo Tosatti
2011-10-03 20:55 ` [Qemu-devel] " Marcelo Tosatti
2011-10-03 20:55 ` [PATCH 1/1] kvm: support TSC deadline MSR Marcelo Tosatti
2011-10-03 20:55   ` [Qemu-devel] " Marcelo Tosatti
2011-10-04 17:53   ` Avi Kivity
2011-10-04 17:53     ` [Qemu-devel] " Avi Kivity
2011-10-04 22:20     ` Marcelo Tosatti
2011-10-04 22:20       ` [Qemu-devel] " Marcelo Tosatti
2011-10-10 14:54       ` Anthony Liguori
2011-10-10 14:54         ` [Qemu-devel] " Anthony Liguori
2011-10-10 14:58         ` Avi Kivity
2011-10-10 14:58           ` [Qemu-devel] " Avi Kivity
2011-10-10 15:10           ` Anthony Liguori [this message]
2011-10-10 15:29             ` Avi Kivity
2011-10-10 14:41 ` [Qemu-devel] [PATCH 0/1] [PULL] qemu-kvm.git uq/master queue Anthony Liguori
2011-10-10 14:48   ` Avi Kivity
2011-10-10 14:48     ` [Qemu-devel] " Avi Kivity
2011-10-10 14:55     ` Anthony Liguori
2011-10-10 14:55       ` [Qemu-devel] " Anthony Liguori
2011-10-10 15:00       ` Avi Kivity
2011-10-10 15:12         ` Anthony Liguori
2011-10-10 15:24           ` Avi Kivity
2011-10-10 15:24             ` [Qemu-devel] " Avi Kivity
2011-10-10 15:36             ` Anthony Liguori
2011-10-10 15:36               ` [Qemu-devel] " Anthony Liguori
2011-10-10 15:41               ` Avi Kivity
2011-10-10 15:41                 ` [Qemu-devel] " Avi Kivity

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=4E930B02.30702@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=jinsong.liu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.