On Thu, May 23, 2013 at 4:41 PM, Kevin Wolf wrote:
> Am 23.05.2013 um 13:57 hat Stefan Hajnoczi geschrieben:
>> On Wed, May 22, 2013 at 03:53:05PM +0200, Kevin Wolf wrote:
>> > Am 16.05.2013 um 21:05 hat Eric Blake geschrieben:
>> > > On 05/16/2013 02:24 AM, Kevin Wolf wrote:
>> > The other thing
Am 23.05.2013 um 13:57 hat Stefan Hajnoczi geschrieben:
> On Wed, May 22, 2013 at 03:53:05PM +0200, Kevin Wolf wrote:
> > Am 16.05.2013 um 21:05 hat Eric Blake geschrieben:
> > > On 05/16/2013 02:24 AM, Kevin Wolf wrote:
> > The other thing that I'm not sure about is whether we should teach QAPI
>
On Wed, May 22, 2013 at 03:53:05PM +0200, Kevin Wolf wrote:
> Am 16.05.2013 um 21:05 hat Eric Blake geschrieben:
> > On 05/16/2013 02:24 AM, Kevin Wolf wrote:
> The other thing that I'm not sure about is whether we should teach QAPI
> to parse certain data structures just into QDicts instead of C s
Am 16.05.2013 um 21:05 hat Eric Blake geschrieben:
> On 05/16/2013 02:24 AM, Kevin Wolf wrote:
> > Okay, let's take a step back here. The idea was more or less that you
> > can specify each BlockDriverState by itself in the end, like this:
> >
> > { "execute": "blockdev-add", "data": {
> > "id
On 05/16/2013 02:24 AM, Kevin Wolf wrote:
> Another thing that we'll probably want from QAPI is some kind of
> inheritance, like this:
>
> { "type": "BlockFileBase", data: { "driver": "str", "cache": "CacheEnum",
> ... }
>
> { "type": "BlockFileNBD", "extends": "BlockFileBase", "data": {
>
[ CCed qemu-devel, Stefan and Luiz ]
Am 15.05.2013 um 19:43 hat Eric Blake geschrieben:
> On 05/15/2013 09:58 AM, Kevin Wolf wrote:
> >
> > Not really. Basically what I have in mind is the obvious mapping of the
> > command line arguments (using the downstream command here because
> > upstream do
