qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] KVM call minutes for Feb 8


From: Anthony Liguori
Subject: Re: [Qemu-devel] KVM call minutes for Feb 8
Date: Tue, 08 Feb 2011 15:11:22 -0600
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.15) Gecko/20101027 Lightning/1.0b1 Thunderbird/3.0.10

On 02/08/2011 01:02 PM, Peter Maydell wrote:
On 8 February 2011 17:13, Markus Armbruster<address@hidden>  wrote:
As far as qdev's concerned, I can see two kinds of to-dos:

* Further develop qdev so that more of the machine init code can becomes
  qdev declarations.  Specific ideas welcome.  Patches even more, as
  always.

* Convert the remaining devices.  They are typically used only with
  oddball machines, which makes the conversion hard to test for anyone
  who's not already using them.

  I've said this before: at some point in time (sooner rather than
  later, if you ask me), we need to shoot the stragglers.  I'm pretty
  optimistic that any victims worth keeping will receive timely
  attention then.
So on IRC pbrook wrote:
<pbrook>  So we have a bunch of devices that nominally claim to use the
qdev infrastructure, but are still making assumptions that qdev was
supposed to remove, so break horribly when you actually try to use it
as intended.

...and my question is: where is the documentation on how to do
a good conversion of a device to qdev, how it works, what the
assumptions you can/can't make are, etc ?

It's basically good OOP modelling and the way qdev is structured today makes it very easy to do bad OOP modelling.

Regards,

Anthony Liguori

  I can't see anything
relevant in the source tree or on the website, but maybe I'm just
looking in the wrong places...

-- PMM





reply via email to

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