mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-25 05:03:05 +00:00
dfbdd75de9
This is slightly different than the PCI class code used by QEMU, which is 0x0100 (mass storage, SCSI controller). We instead use 0x0180 to indicate a mass storage controller with a non-standardized/vendor specific programming interface (ref: PCI Code and ID Assignment Specification). SCSI isn't really accurate for a virtio-blk device (our implementation does not accept SCSI commands at all, although there is a pre-virtio-1.0 option for sending them). The Linux virtio-blk guest driver does not care about the PCI class code either way (it only matches on the PCI vendor+device ID range assigned for virtio devices and uses the virtio-specific device type to distinguish between e.g. virtio-blk and virtio-scsi), so it should be fine to use the Other/Vendor-specific subclass code. lspci diff: -00:04.0 Unclassified device [00ff]: Red Hat, Inc. Virtio block device [1af4:1042] (rev 01) +00:04.0 Mass storage controller [0180]: Red Hat, Inc. Virtio block device [1af4:1042] (rev 01) BUG=None TEST=lspci -vvvnnn # "Mass storage controller" for block devices Change-Id: I7958dbb1c197fe52afb386ebb9afa9f5107a56cd Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4740712 Reviewed-by: Morg <morg@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> |
||
|---|---|---|
| .. | ||
| goldens | ||
| backcompat.rs | ||
| block.rs | ||
| boot.rs | ||
| fs.rs | ||
| pci_hotplug.rs | ||
| prebuilts.rs | ||
| snd.rs | ||
| suspend_resume.rs | ||
| vsock.rs | ||