Carsten Otte wrote:
> Christian Borntraeger wrote:
>>> It is not yet updated to latest virtio & latest kvm.
>>> This version uses a pci device for virtio. Since I'm think Rusty's
>>> config space does not matches
>>> pci config space I might consider changing it. (Preferably not, maybe
>>> I'll start using it until we'll have the windows
>>> implementation).
>>> I'll start work on it on Sunday.
>>
>> I currently try to use Rusty's config space as we dont have a PCI bus.
>> Carsten told me that HPA suggested to split CONFIG_PCI in a way to use
>> the hardware independent data structures without providing the hardware.
>>
>> Carsten do you still remember the full details?
> *Shrug*. I think Peter suggested that we'd use a PCI bus type, and PCI
> IDs for device identification. We're not going to use PCI to do I/O, and
> we're not going to use IRQ (HPA: irq == 0 is a valid value, which means
> that the PCI device does not have an irq). He suggested to look at the
> virtio bus that he contributed to Rusty's lguest code as an example.
Yep, that's pretty much it.
Config space above 0x3F is device-specific; we can add well-known
structures for virtio there is appropriate, preferrably via a PCI
"capability" structure.
-hpa
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
kvm-devel mailing list
kvm-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-devel
