qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PATCH v2 0/7] APIC/IOAPIC cleanup


From: Anthony Liguori
Subject: Re: [Qemu-devel] [PATCH v2 0/7] APIC/IOAPIC cleanup
Date: Sun, 22 Aug 2010 16:07:51 -0500
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.11) Gecko/20100713 Lightning/1.0b1 Thunderbird/3.0.6

On 08/22/2010 02:44 PM, Avi Kivity wrote:
No more MI diamond and all devices have DeviceStates. Coincidentally, it matches more closely how hardware works..



Well, I agree, but I honestly lost the context. How does this relate to the APIC and cpu hotplug?

I'll take the opportunity to say that we should be using a language that has first-class (...) support for these concepts instead of having to divine them from the code.

At the risk of sounding uncool, I think what we really need is a UML diagram describing the device tree. It's really not that much more difficult to create a similar mess in C++.

Regards,

Anthony Liguori

Generally speaking, any time we have one device that needs to sit on multiple busses, we're going to have to model it in this fashion.

We'll just have to address them one by one then. Perhaps if many come up we can try a generic solution.





reply via email to

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