All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: Juan Quintela <quintela@redhat.com>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
	Avi Kivity <avi@redhat.com>,
	Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] Re: [PATCH v2 12/15] monitor: Add basic device state visualization
Date: Tue, 25 May 2010 00:12:30 +0200	[thread overview]
Message-ID: <4BFAF9CE.8010706@web.de> (raw)
In-Reply-To: <4BFAF477.4030303@linux.vnet.ibm.com>

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

Anthony Liguori wrote:
> On 05/24/2010 03:35 PM, Jan Kiszka wrote:
>> In contrast to save/loadvm, device_show does not provide a
>> backward-compatible output. Not only field names can change (as a result
>> of internal refactoring),
> 
> Field names could change, but that seems unlikely and unnecessary.

Actually, this may happen to improve the output format for device_show,
either via renaming the fields or annotating it (once we have the latter
mechanism).

> 
>>   fields may even disappear,
> 
> That would break live migration. 

Nope. We can (and I think we did before) perfectly read some field up to
version X and convert it into the new format but skip that field for X+1
upward.

> The output of device_show when
> specifying -M pc-0.13 should always be the same.  If it's not, I believe
> that's a bug.
> 
> The output of device_show across multiple qemu versions without
> specifying a -M could certainly be different but that's to be expected
> since you have a different hardware model.

It will be different as soon as the version_id of a dumped vmstate
changes, even independent of -M.

Jan


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

  reply	other threads:[~2010-05-24 22:13 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-22  8:17 [Qemu-devel] [PATCH v2 00/15] Basic device state visualization Jan Kiszka
2010-05-22  8:17 ` [Qemu-devel] [PATCH v2 01/15] Add dependency of JSON unit tests on config-host.h Jan Kiszka
2010-05-22  8:17 ` [Qemu-devel] [PATCH v2 02/15] qdev: Fix scanning across single-bus devices Jan Kiszka
2010-05-29  7:38   ` Markus Armbruster
2010-05-29  7:56     ` Jan Kiszka
2010-05-31  9:45     ` Gerd Hoffmann
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 03/15] qdev: Allow device addressing via 'driver.instance' Jan Kiszka
2010-05-29  7:50   ` Markus Armbruster
2010-05-29  8:09     ` Jan Kiszka
2010-05-31  8:43       ` Markus Armbruster
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 04/15] qdev: Convert device and bus lists to QTAILQ Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 05/15] qdev: Allow device specification by qtree path for device_del Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 06/15] qdev: Push QMP mode checks into qbus_list_bus/dev Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 07/15] monitor: Add completion for qdev paths Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 08/15] Add base64 encoder/decoder Jan Kiszka
2010-05-22 13:59   ` Blue Swirl
2010-05-23  7:55     ` Jan Kiszka
2010-05-23  8:48       ` Avi Kivity
2010-05-23 10:04         ` Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 09/15] QMP: Reserve namespace for complex object classes Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 10/15] Add QBuffer Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 11/15] monitor: return length of printed string via monitor_[v]printf Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 12/15] monitor: Add basic device state visualization Jan Kiszka
2010-05-22 18:55   ` [Qemu-devel] " Avi Kivity
2010-05-23  7:57     ` Jan Kiszka
2010-05-23  8:44       ` Avi Kivity
2010-05-23 10:03         ` Jan Kiszka
2010-05-23 10:42           ` Avi Kivity
2010-05-29  8:00         ` Markus Armbruster
2010-05-29  8:14           ` Jan Kiszka
2010-05-30  8:26             ` Avi Kivity
2010-05-30 12:36               ` Jan Kiszka
2010-05-31  8:46                 ` Markus Armbruster
2010-05-31  8:58                   ` Jan Kiszka
2010-05-31 11:07                     ` Markus Armbruster
2010-05-31 11:11                       ` Jan Kiszka
2010-05-24 12:51       ` Luiz Capitulino
2010-05-24 20:22         ` Anthony Liguori
2010-05-24 20:22     ` Anthony Liguori
2010-05-24 20:35       ` Jan Kiszka
2010-05-24 21:49         ` Anthony Liguori
2010-05-24 22:12           ` Jan Kiszka [this message]
2010-05-24 22:27             ` Anthony Liguori
2010-05-25  7:23       ` Avi Kivity
2010-05-25 13:03         ` Anthony Liguori
2010-05-25 13:19           ` Avi Kivity
2010-05-25 13:31             ` Anthony Liguori
2010-05-25 13:41               ` Avi Kivity
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 13/15] QMP: Teach basic capability negotiation to python example Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 14/15] QMP: Fix python helper /wrt long return strings Jan Kiszka
2010-05-22  8:18 ` [Qemu-devel] [PATCH v2 15/15] QMP: Add support for buffer class to qmp python helper Jan Kiszka
2010-05-22 14:05 ` [Qemu-devel] [PATCH v2 00/15] Basic device state visualization Blue Swirl
2010-05-23  7:55   ` Jan Kiszka

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=4BFAF9CE.8010706@web.de \
    --to=jan.kiszka@web.de \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    /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.