RFC s390x: cut down on unattached devices
Status from this message: Queued to s390-next.
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 21 repliesApplied
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | s390x/css: attach css bridgehw/ | +2 | 2 replies | |
| 2/2 | s390x: attach autogenerated nicshw/ | +2 | 4 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Christian Borntraeger | David Hildenbrand | Bjoern Walk |
|---|---|---|---|
| Series | R-b | T-b | |
| 1/2 | R-b | ||
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Cover letter [Qemu-devel] [PATCH RFC 0/2] s390x: cut down on unattached devices
info qom-tree shows several devices under unattached that probably should go somewhere.
The css bridge should attach to the machine, as it has a similar purpose as e.g. a pci host bridge.
The autogenerated network devices should be in the same bucket as any other device; I'm just not sure about the way I went about it.
The zpci devices are still problematic: I don't have a good idea where they should show up.
Remaining in the unattached container are the sysbus, memory regions and cpus.
Cornelia Huck (2):
s390x/css: attach css bridge
s390x: attach autogenerated nics
hw/s390x/css-bridge.c | 2 ++ hw/s390x/s390-virtio-ccw.c | 2 ++ 2 files changed, 4 insertions(+)
Signature · 1 line
2.13.6