[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER

From: Avi Kivity
Subject: Re: [Qemu-devel] [PATCH] Change virtio-console to PCI_CLASS_SERIAL_OTHER
Date: Sun, 31 May 2009 17:32:49 +0300
User-agent: Thunderbird (X11/20090320)

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

reply via email to

[Prev in Thread] Current Thread [Next in Thread]