From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MjBpk-0001Uy-Tg for qemu-devel@nongnu.org; Thu, 03 Sep 2009 08:54:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MjBpg-0001UI-0a for qemu-devel@nongnu.org; Thu, 03 Sep 2009 08:54:36 -0400 Received: from [199.232.76.173] (port=45916 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MjBpf-0001UF-Sx for qemu-devel@nongnu.org; Thu, 03 Sep 2009 08:54:31 -0400 Received: from mx20.gnu.org ([199.232.41.8]:31536) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MjBpf-0007Rv-F3 for qemu-devel@nongnu.org; Thu, 03 Sep 2009 08:54:31 -0400 Received: from mx1.redhat.com ([209.132.183.28]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MjBpe-00022k-7T for qemu-devel@nongnu.org; Thu, 03 Sep 2009 08:54:30 -0400 From: Amit Shah Date: Thu, 3 Sep 2009 18:23:29 +0530 Message-Id: <1251982412-11870-1-git-send-email-amit.shah@redhat.com> Subject: [Qemu-devel] Multiple port support for virtio-console List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, kvm@vger.kernel.org Hello all, Here is a new iteration of the patch series that implements a transport for guest and host communications. I've tested for compatibility (old qemu & new kernel, new qemu & old kernel, new qemu & new kernel) and it all works fine*. There are a few items on my todo list but this works well. New since last send: - live migration support** - write path in the guest driver can now be called from irq context TODO: - Convert all config writes to little endian in qemu / convert from little endian to host endian in guest - Address a few FIXMEs spread in the code - Introduce a watermark to stop a rogue host process flooding guest with data Conditions: * Heavy IO on an hvc port and a non-hvc port causes memory corruption each time, same place. It could be realted to locking but I doubt that. This still has to be sorted out ** qemu now caches buffers till a char device is opened or till an entire write request is not received in userspace. These buffers aren't yet migrated. Please review. Amit