[Top][All Lists]

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

Re: [Qemu-devel] [PATCH 00/18] qom: dynamic properties and composition t

From: Avi Kivity
Subject: Re: [Qemu-devel] [PATCH 00/18] qom: dynamic properties and composition tree
Date: Thu, 01 Dec 2011 16:48:56 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:8.0) Gecko/20111115 Thunderbird/8.0

On 12/01/2011 04:42 PM, Anthony Liguori wrote:
>> We need good tools to allow easy review of the ABI bits hiding in
>> patches, and to maintain ABI compatibility.  Something like
>> qemu-print-abi that dumps all properties for all devices.  Patches could
>> show the ABI changes by including a diff of the output of this program
>> from before and after a change, and we could add similar tests for
>> backwards compatibility.
> I'm not sure that we want this interface to be backwards compatible. 
> I actually think we should provide a higher level interface that's
> explicitly there for compatibility.  Probably in the form of a C
> library that can be documented and reasoned with better.

Does this force anyone who wants a stable ABI to use this library?

I don't have a good picture of this library.  If FooState has a bar
propery, do you generate qemu_foo_get_bar() and qemu_foo_set_bar()

error compiling committee.c: too many arguments to function

reply via email to

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