Hi,
* the SIZE property patch: Msg-Id:<4bb206b9.80...@collabora.co.uk>
Fine with me.
* the socket reconnect patch: Msg-Id:<4b18055b.1030...@collabora.co.uk>
Not sure yet.
If we can get these patches sorted out, the only outstanding issues are
where the EGD protocol support and rate limiting should go.
I think it makes sense to have a separate chardev backend for it, so you
can easily hook it up to either virtio-rng or something else, i.e.
define a chardev for the egd connection like this:
-chardev backend=egd,id=egd,server=$address,$rate-limit-options-here
then link it to virtio-rng ...
-device virtio-rng-pci,chardev=egd
... or virtio-serial ...
-device virtserialport,chardev=egd,name=org.qemu.egd
... or a emulated 16650 ....
-device isa-serial,chardev=egd
... depending on what you prefer and what your guest can handle.
It might make sense to have the reconnect logic in the egd chardev
backend then, thereby obsoleting the socket reconnect patch.
cheers,
Gerd
