qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Questions about chardev (and ps/2 mouse)
Date: Tue, 5 Apr 2011 21:45:48 +0100	[thread overview]
Message-ID: <BANLkTi=852nKvBOJL1DrkDG3Sh_04q4=JA@mail.gmail.com> (raw)
In-Reply-To: <4D9B7BA6.3020800@codemonkey.ws>

On 5 April 2011 21:29, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 04/05/2011 01:55 PM, Brian Wheeler wrote:
>>
>> I'm trying to disable the ps/2 mouse in favor of the serial mouse
>> provided by -chardev msmouse since the ps/2 mouse has had lots of
>> problems with older OSes (OpenStep, OS/2, Win 3.1, etc).  I've got a
>> couple of questions:
>>
>> 1) If I change a VMState something by appending a field (i.e.
>> "unplugged"), do I have to update version_id?
>
> Yes.  You can use a subsection though to avoid bumping the version_id.
>
>>   How do the
>> minimum_version_id{,_old} fields fit in?
>
> This is for load, not save.  It's used to basically deprecate loading from
> very old versions.

There was an email thread about this recently:
http://web.archiveorange.com/archive/v/1XS1vynR1fW0cG5xll6r

I need to go back and reread it and propose a docs patch
for people to shoot down; I think having a clear description
of "what do I have to do if I've added a new field to a device
model" is important, because that will often be the only
interaction a developer has with the migration/vmstate stuff.

-- PMM

      reply	other threads:[~2011-04-05 20:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 18:55 [Qemu-devel] Questions about chardev (and ps/2 mouse) Brian Wheeler
2011-04-05 19:36 ` Brian Wheeler
2011-04-05 20:29 ` Anthony Liguori
2011-04-05 20:45   ` Peter Maydell [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='BANLkTi=852nKvBOJL1DrkDG3Sh_04q4=JA@mail.gmail.com' \
    --to=peter.maydell@linaro.org \
    --cc=anthony@codemonkey.ws \
    --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).