-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'mst/tags/for_anthony' into staging
pci,virtio This further optimizes MSIX handling in virtio-pci. Also included is pci cleanup by Paolo, and pci device assignment fix by Alex. Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> * mst/tags/for_anthony: pci-assign: Enable MSIX on device to match guest pci: use constants for devices under the 1B36 device ID, document them ivshmem: use symbolic constant for PCI ID, add to pci-ids.txt virtio-9p: use symbolic constant, add to pci-ids.txt reorganize pci-ids.txt docs: move pci-ids.txt to docs/specs/ vhost: backend masking support vhost: set started flag while start is in progress virtio-net: set/clear vhost_started in reverse order virtio: backend virtqueue notifier masking virtio-pci: cache msix messages kvm: add stub for update msi route msix: add api to access msix message virtio: don't waste irqfds on control vqs
- Loading branch information
Showing
19 changed files
with
437 additions
and
100 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
|
||
PCI IDs for qemu | ||
================ | ||
|
||
Red Hat, Inc. donates a part of its device ID range to qemu, to be used for | ||
virtual devices. The vendor IDs are 1af4 (formerly Qumranet ID) and 1b36. | ||
|
||
Contact Gerd Hoffmann <kraxel@redhat.com> to get a device ID assigned | ||
for your devices. | ||
|
||
1af4 vendor ID | ||
-------------- | ||
|
||
The 1000 -> 10ff device ID range is used as follows for virtio-pci devices. | ||
Note that this allocation separate from the virtio device IDs, which are | ||
maintained as part of the virtio specification. | ||
|
||
1af4:1000 network device | ||
1af4:1001 block device | ||
1af4:1002 balloon device | ||
1af4:1003 console device | ||
1af4:1004 SCSI host bus adapter device | ||
1af4:1005 entropy generator device | ||
1af4:1009 9p filesystem device | ||
|
||
1af4:10f0 Available for experimental usage without registration. Must get | ||
to official ID when the code leaves the test lab (i.e. when seeking | ||
1af4:10ff upstream merge or shipping a distro/product) to avoid conflicts. | ||
|
||
1af4:1100 Used as PCI Subsystem ID for existing hardware devices emulated | ||
by qemu. | ||
|
||
1af4:1110 ivshmem device (shared memory, docs/specs/ivshmem_device_spec.txt) | ||
|
||
All other device IDs are reserved. | ||
|
||
1b36 vendor ID | ||
-------------- | ||
|
||
The 0000 -> 00ff device ID range is used as follows for QEMU-specific | ||
PCI devices (other than virtio): | ||
|
||
1b36:0001 PCI-PCI bridge | ||
1b36:0002 PCI serial port (16550A) adapter (docs/specs/pci-serial.txt) | ||
1b36:0003 PCI Dual-port 16550A adapter (docs/specs/pci-serial.txt) | ||
1b36:0004 PCI Quad-port 16550A adapter (docs/specs/pci-serial.txt) | ||
|
||
All these devices are documented in docs/specs. | ||
|
||
The 0100 device ID is used for the QXL video card device. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.