Arnd Bergmann wrote: > On Wednesday 04 April 2007, H. Peter Anvin wrote: >> Note that at least for PIO-based devices, there is nothing that says you >> can't implement PCI over another transport, if you wish. It's really >> just a very simple RPC protocol. > > The PIO aspect of PCI is simple, yes, except on architectures that don't > have the concept of PIO or even uncached memory, but even that can > be done by defining readl/writel/inl/outl/... as hcalls. > > The tricky part about PCI is the device probing, everything about config > space accesses, interrupt swizzling, bus/device/function numbers and > base address registers becomes a pointless excercise when the other side > is just faking it. Configuration space access is platform-dependent. It's only defined to work in a specific way on x86 platforms. "Interrupt swizzling" is really totally independent of PCI. ALL PCI really provides is up to four interrupts per device (not counting MSI/MSI-X) and an 8-bit writable field which the platform can choose to use to hold interrupt information. That's all. The rest is all platform information. PCI enumeration is hardly complex. Most of the stuff that doesn't apply to you you can generally ignore, as is done by other busses like HyperTransport when they emulate PCI. That being said, on platforms which are PCI-centric, such as x86, this of course makes it a lot easier to produce virtual devices which work across hypervisors, since the device model, of *any* operating system is set up to handle them. -hpa _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
