[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] virtio-serial: An interface for host-guest communication
From: |
Amit Shah |
Subject: |
[Qemu-devel] virtio-serial: An interface for host-guest communication |
Date: |
Mon, 27 Jul 2009 23:34:32 +0530 |
Hello all,
This are the latest version of the patches.
Lots of things have changed since the last submission. A few of
which I remember:
- VNC copy / paste works* (* conditions apply)
- client vnc copies get propagated to guest port 3 (/dev/vmch3)
- guest writes to port 3 (/dev/vmch3) go straight to client's clipboard
- sysfs hooks to autodiscover ports
- support for 64 ports in this version (MAX_VIRTIO_SERIAL_PORTS). More
ports can be added by introducing a new feature flag to maintain
backward compat. However, till this code gets accepted upstream, the
value of that #define can change. I think 64 ports are enough for
everyone.
- remove support for control queue (though this queue could make a
comeback for just one use-case that I can currently think of:
to prevent rogue (host) userspace putting lots of data into a guest
that goes unconsumed for a while, increasing the memory pressure. To
prevent this a threshold level can be decided upon and a control
message can be sent to host userspace to prevent any more writes
to the port.
- numerous fixes
There still exist a few kmalloc/kfree-related debug logs that spew up
in the guest but I haven't been able to track them down.
As for the merge with virtio-console, Christian has voiced some oppostion
to that idea. For the merge to happen, the kernel folks have to agree
in merging the driver as well and I can proceed once we have a resolution
on this.
Other than that, a few more rebases have to be done to the qemu code to
make it apply to qemu-upstream.
Please give this a good review.
Thanks,
Amit.