From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MVUZB-00079w-1l for qemu-devel@nongnu.org; Mon, 27 Jul 2009 14:04:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MVUZ6-00075H-CT for qemu-devel@nongnu.org; Mon, 27 Jul 2009 14:04:52 -0400 Received: from [199.232.76.173] (port=51908 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MVUZ6-000750-6s for qemu-devel@nongnu.org; Mon, 27 Jul 2009 14:04:48 -0400 Received: from mx2.redhat.com ([66.187.237.31]:44264) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MVUZ5-0004cA-Ii for qemu-devel@nongnu.org; Mon, 27 Jul 2009 14:04:47 -0400 From: Amit Shah Date: Mon, 27 Jul 2009 23:34:32 +0530 Message-Id: <1248717876-17630-1-git-send-email-amit.shah@redhat.com> Subject: [Qemu-devel] virtio-serial: An interface for host-guest communication List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: virtualization@lists.linux-foundation.org Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org 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.