virtio implementation (draft VI)
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 32 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | virtio interfacedrivers/ drivers/ drivers/ +6 more | +434 | 11 replies | |
| 2/3 | virtio ring implementationarch/ drivers/ drivers/ +2 more | +442 | 13 replies | |
| 3/3 | virtio module alias supportdrivers/ scripts/ | +27 | 10 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] virtio implementation (draft VI)
I'm not reposting the drivers this time since they haven't changed significantly. See http://lguest.ozlabs.org/patches for the whole thing, from new-io.patch onwards).
Changes since last version:
- Switch to our own bus implementation, rather than relying on an implementation-specific bus to back this up.
- Make virtio_config_ops much higher-level, don't assume layout of config space.
- Expose "struct virtqueue" again and move ops inside that.
- virtio_ring uses 64 bit address, 32 bit length, not addr64 + offset16 + len16.
- flags in virtio_ring to allow suppression of interrupts (by guest) or notifications (by host).
I'm not too unhappy with this as it stands. Feedback welcome!
Cheers,
Rusty.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/