|
From: | Anthony Liguori |
Subject: | Re: [Qemu-devel] [RFC] Plan for moving forward with QOM |
Date: | Thu, 15 Sep 2011 15:52:09 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110516 Lightning/1.0b2 Thunderbird/3.1.10 |
On 09/15/2011 03:23 PM, Avi Kivity wrote:
On 09/15/2011 04:26 PM, Anthony Liguori wrote:I think this model is the closest to what we have today and is the most obvious. For something like ne2k, I would expect: class NE2000 : public Device { // ne2k public functions }; class PCI_NE2000 : public PciDevice { // implement PCI functions by calling ne2k public functions NE2000 ne2k; }; class ISA_NE2000 : public IsaDevice { // implement ISA functions by calling ne2k public functions NE2000 ne2k; };Also, NE2000 methods have to call ISA_NE2000 and PCI_NE2000 methods, yes?
I don't think so. The NE2k would export an IRQ and the ISA_NE2K and PCI_NE2k would have to route that IRQ. But I think that's the extent of the communication in that direction.
Am I missing something? Regards, Anthony Liguori That's
going to be more difficult. Not impossible, just hard. It's probably going to involve device specific code that models what type of glue was used for that particular device/bus combo.
[Prev in Thread] | Current Thread | [Next in Thread] |