qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [RESEND][PATCH] KVM: x86: Refactor persistent CPU state
Date: Mon, 29 Jun 2009 21:23:02 +0200	[thread overview]
Message-ID: <4A491496.3020803@web.de> (raw)
In-Reply-To: <4A491157.1030206@codemonkey.ws>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

Anthony Liguori wrote:
> Blue Swirl wrote:
>> On 6/27/09, Jan Kiszka <jan.kiszka@web.de> wrote:
>>  
>>> This patch aligns the KVM-related layout and encoding of the CPU state
>>>  to be saved to disk or migrated with qemu-kvm. The major differences
>>> are
>>>  reordering of fields and a compressed interrupt_bitmap into a single
>>>  number as there can be no more than one pending IRQ at a time.
>>>     
>>
>> This changes the savevm format, shouldn't you bump the version?
>>   
> 
> Practically speaking, it's been bumped for KVM already in this release
> cycle so changing the format without bumping the version should be
> okay.  It may interfere with kvm-XX releases but I'm not sure whether
> that's an issue for us and how we should handle that long term.

That particular patch is already part of kvm-87. Here we are just
aligning both code bases, and that even on the same format version number.

> 
> I'm assuming Jan thought all of this through ahead of time and just
> forgot to explicitly state the reasoning for not bumping the version :-)

Of course, I considered every possible case in every detail. :)

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

      reply	other threads:[~2009-06-29 19:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-27  7:27 [Qemu-devel] [RESEND][PATCH] KVM: x86: Refactor persistent CPU state Jan Kiszka
2009-06-28 15:40 ` Blue Swirl
2009-06-28 18:10   ` [Qemu-devel] " Jan Kiszka
2009-06-29 19:09   ` [Qemu-devel] " Anthony Liguori
2009-06-29 19:23     ` Jan Kiszka [this message]

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=4A491496.3020803@web.de \
    --to=jan.kiszka@web.de \
    --cc=aliguori@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).