Hi Rusty,
I've written a PCI virtio transport and noticed something strange. All
current in-tree virtio devices register ID tables that match a specific
device ID, but any vendor ID.
This is incompatible with using PCI vendor/device IDs for virtio
vendor/device IDs since vendors control what device IDs mean. A simple
solution would be to assign a fixed vendor ID to all current virtio
devices. This doesn't solve the problem completely though since you
would create a conflict between the PCI vendor ID space and the virtio
vendor ID space.
The only solutions seem to be virtualizing the virtio vendor/device IDs
(which is what I'm currently doing) or to mandate that the virtio vendor
ID be within the PCI vendor ID space. It's probably not necessary to
make the same requirement for device IDs though.
What are your thoughts?
Regards,
Anthony Liguori
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
