Since virtio devices can live on two busses (sysbus with Syborg or PCI),
we need to introduce a set of virtio specific functions.
...
Inside the VirtIODevice, there would be corresponding function pointers,
and depending on whether it was a PCI device or a Syborg device, it would
call
On Wed, Feb 10, 2010 at 11:13 PM, Anthony Liguori anth...@codemonkey.ws wrote:
On 02/10/2010 02:41 PM, Richard Henderson wrote:
On 02/10/2010 11:29 AM, Anthony Liguori wrote:
void *pci_memory_map(PCIDevice *dev, pcibus_t addr, pcibus_t *plen, int
is_write);
void pci_memory_unmap(PCIDevice
On Wed, Feb 10, 2010 at 12:01 AM, Anthony Liguori aligu...@us.ibm.com wrote:
This is a work in progress that I wanted to share giving some of the
discussions
around rwhandlers. The idea is to make PCI devices have a common set of
functions to interact with the CPU that is driven entirely
On 02/10/2010 12:34 PM, Blue Swirl wrote:
On Wed, Feb 10, 2010 at 12:01 AM, Anthony Liguorialigu...@us.ibm.com wrote:
This is a work in progress that I wanted to share giving some of the discussions
around rwhandlers. The idea is to make PCI devices have a common set of
functions to
On 02/10/2010 11:29 AM, Anthony Liguori wrote:
void *pci_memory_map(PCIDevice *dev, pcibus_t addr, pcibus_t *plen, int
is_write);
void pci_memory_unmap(PCIDevice *dev, void *buf, pcibus_t *plen, int
is_write, pcibus_t access_len);
Are these functions intended to be controllable by the root
On 02/10/2010 02:41 PM, Richard Henderson wrote:
On 02/10/2010 11:29 AM, Anthony Liguori wrote:
void *pci_memory_map(PCIDevice *dev, pcibus_t addr, pcibus_t *plen, int
is_write);
void pci_memory_unmap(PCIDevice *dev, void *buf, pcibus_t *plen, int
is_write, pcibus_t access_len);
Are these
