Re: [Qemu-devel] RFC: -object vs -chardev creation order

2015-03-18 Thread Daniel P. Berrange
On Wed, Mar 18, 2015 at 10:43:25AM +0100, Markus Armbruster wrote: > "Daniel P. Berrange" writes: > > A third option is to not process -object args in one go, instead process > > each type of object at a time. eg we'd first create all the > > -object tls-credential instances, then create the -char

Re: [Qemu-devel] RFC: -object vs -chardev creation order

2015-03-18 Thread Markus Armbruster
"Daniel P. Berrange" writes: > The current QEMU startup code will create -chardev backends first, then > create -object backends, then -fsdev backends and so on, in some pretty > arbitrary order of types. > > There is already a dependancy from the rng-egd object type, which has a > link to a char

Re: [Qemu-devel] RFC: -object vs -chardev creation order

2015-03-18 Thread Paolo Bonzini
On 17/03/2015 20:08, Daniel P. Berrange wrote: > A third option is to not process -object args in one go, instead process > each type of object at a time. eg we'd first create all the > -object tls-credential instances, then create the -chardev instances, > then create the -object rng-egd instanc

[Qemu-devel] RFC: -object vs -chardev creation order

2015-03-17 Thread Daniel P. Berrange
The current QEMU startup code will create -chardev backends first, then create -object backends, then -fsdev backends and so on, in some pretty arbitrary order of types. There is already a dependancy from the rng-egd object type, which has a link to a chardev, which requires -chardev options be pr