qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH] machine: set default kernel_cmdline in machine_


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH] machine: set default kernel_cmdline in machine_initfn()
Date: Thu, 29 May 2014 17:47:45 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0

Il 29/05/2014 15:26, Andreas Färber ha scritto:
Am 29.05.2014 15:21, schrieb Marcel Apfelbaum:
On Thu, 2014-05-29 at 15:08 +0200, Igor Mammedov wrote:
On Thu, 29 May 2014 15:56:16 +0300
Marcel Apfelbaum <address@hidden> wrote:
On Thu, 2014-05-29 at 14:40 +0200, Igor Mammedov wrote:
Maybe we can hack QemuOpts to do s/foo_moo/foo-moo/ ?
Than there won't be need for an explicit conversion and it could be reused by 
others,
including X86CPU.
I like this idea, but this can't be generic for all QemuOpts right? Do you
mean adding a flag specifying we want this conversion?
Flag would be less risky than doing it for all QemuOpts unconditionally.
It would open road for conversion per a QemuOpts which probably should be
done eventually if options are translated into properties.
Sounds fine, I can go for it.
Andreas, do you agree?

Whatever works to get a sane QOM ABI without bad side-effects.

What exactly is part of the API/ABI? Is any tool actually using qom-list/qom-get/qom-set? Because if not, it's pointless to stick to a well-defined API/ABI.

In any case, I guess we could just s/_/-/g in object_set_property?

Paolo




reply via email to

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