Extra capabilities for device assignment
Status from this message: Applied, thanks. EFAULT is not the best error return, though.
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest5 patches 6 repliesApplied
- v15 patches 3 repliesSuperseded
Changes in v2 from the cover letter
- Reimplement 2/5 to remove more cruft
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | device-assignment: Fix off-by-one in header checkhw/ | +2 | 0 replies | |
| 2/5 | pci: Remove PCI_CAPABILITY_CONFIG_*hw/ hw/ | +3 | 0 replies | |
| 3/5 | pci: Error on PCI capability collisionshw/ | +14 | 0 replies | |
| 4/5 | device-assignment: Error checking when adding capabilitieshw/ | +7 | 0 replies | |
| 5/5 | device-assignment: pass through and stub more PCI capshw/ | +256 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/5] Extra capabilities for device assignment
v2:
- Reimplement 2/5 to remove more cruft
v1:
Now that we've got PCI capabilities cleaned up and device assignment using them, we can add more capabilities to be guest visible. This adds minimal PCI Express, PCI-X, and Power Management, along with direct passthrough Vital Product Data and Vendor Specific capabilities. With this, devices like tg3, bnx2, vxge, and potentially quite a few others that didn't work previously should be happier. Thanks,
Alex
---
Alex Williamson (5):
device-assignment: pass through and stub more PCI caps
device-assignment: Error checking when adding capabilities
pci: Error on PCI capability collisions
pci: Remove PCI_CAPABILITY_CONFIG_*
device-assignment: Fix off-by-one in header check
hw/device-assignment.c | 279 ++++++++++++++++++++++++++++++++++++++++++++++-- hw/pci.c | 14 ++ hw/pci.h | 5 - 3 files changed, 279 insertions(+), 19 deletions(-)