From: Avi Kivity <avi@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Mark McLoughlin <markmc@redhat.com>,
dlaor@redhat.com, ajax@redhat.com,
Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER
Date: Sun, 31 May 2009 17:32:49 +0300 [thread overview]
Message-ID: <4A229511.8000907@redhat.com> (raw)
In-Reply-To: <4A1FAFF7.3080808@us.ibm.com>
Anthony Liguori wrote:
> Mark McLoughlin wrote:
>
>> On Fri, 2009-05-29 at 00:45 +0300, Dor Laor wrote:
>>
>> The more I think about it, no matter how much linear ABI versioning
>> sucks, it's possibly the only way to solve this in a reasonably usable
>> manners. Distros would just have to suck it up and agree that if they
>> cherry-pick an ABI changing patch, they must update the entire ABI to
>> the newer upstream ABI version.
>>
>>
>
> Can we somehow utilize the save/restore versioning infrastructure? I
> think the general idea of universally versioning devices is not a bad
> one but I'm not sure whether we need an additional version id or whether
> we can just piggy back on the savevm version.
>
The savevm version can be updated due to fixes in the savevm protocol
that don't affect the guest visible information at all.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-05-31 14:35 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 17:14 [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER Mark McLoughlin
2009-05-24 9:11 ` Avi Kivity
2009-05-27 14:21 ` Anthony Liguori
2009-05-27 17:42 ` Mark McLoughlin
2009-05-27 22:37 ` Anthony Liguori
2009-05-28 9:33 ` Mark McLoughlin
2009-05-28 9:44 ` Anthony Liguori
2009-05-28 12:53 ` Paul Brook
2009-05-28 12:56 ` Anthony Liguori
2009-05-28 13:22 ` Paul Brook
2009-05-28 13:29 ` Anthony Liguori
2009-05-28 21:45 ` Dor Laor
2009-05-29 9:43 ` Mark McLoughlin
2009-05-29 9:50 ` Anthony Liguori
2009-05-31 14:32 ` Avi Kivity [this message]
2009-05-29 9:55 ` Anthony Liguori
2009-05-29 10:09 ` Mark McLoughlin
2009-05-31 14:47 ` Dor Laor
2009-06-02 8:49 ` Mark McLoughlin
2009-06-02 13:08 ` Dor Laor
2009-06-02 13:39 ` Mark McLoughlin
2009-05-31 14:35 ` Dor Laor
2009-06-02 8:49 ` Mark McLoughlin
2009-05-28 13:04 ` Daniel P. Berrange
2009-05-28 13:19 ` Anthony Liguori
2009-05-31 18:48 ` Jamie Lokier
2009-05-28 13:20 ` Paul Brook
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=4A229511.8000907@redhat.com \
--to=avi@redhat.com \
--cc=ajax@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=dlaor@redhat.com \
--cc=markmc@redhat.com \
--cc=paul@codesourcery.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.