From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MEL2o-0006eY-C9 for qemu-devel@nongnu.org; Wed, 10 Jun 2009 06:28:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MEL2j-0006aw-Eo for qemu-devel@nongnu.org; Wed, 10 Jun 2009 06:28:33 -0400 Received: from [199.232.76.173] (port=46885 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MEL2j-0006ao-8Q for qemu-devel@nongnu.org; Wed, 10 Jun 2009 06:28:29 -0400 Received: from mx2.redhat.com ([66.187.237.31]:52818) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MEL2i-00078I-Oq for qemu-devel@nongnu.org; Wed, 10 Jun 2009 06:28:29 -0400 Date: Wed, 10 Jun 2009 15:58:24 +0530 From: Amit Shah Subject: Re: [Qemu-devel] [PATCH] virtio-serial: PCI device for simple host <-> guest communication Message-ID: <20090610102823.GA12327@amit-x200.pnq.redhat.com> References: <1244565768-9103-1-git-send-email-amit.shah@redhat.com> <1244565768-9103-2-git-send-email-amit.shah@redhat.com> <1244565768-9103-3-git-send-email-amit.shah@redhat.com> <1244565768-9103-4-git-send-email-amit.shah@redhat.com> <20090609181714.GB11485@amd.home.annexia.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090609181714.GB11485@amd.home.annexia.org> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Richard W.M. Jones" Cc: qemu-devel@nongnu.org On (Tue) Jun 09 2009 [19:17:14], Richard W.M. Jones wrote: > On Tue, Jun 09, 2009 at 10:12:48PM +0530, Amit Shah wrote: > [...] > > Are you going to post the virtio driver for the Linux kernel later? A few cleanups needed. I'll get to that right now. > > +DEF("virtioserial", HAS_ARG, QEMU_OPTION_virtioserial, \ > > + "-virtioserial c\n" \ > > + " define virtio serial device\n") > > Can it be made to look like a real serial port, ie. > '-serial dev,model=virtio' ? Yes, this part is still in flux: there are a few more parameters that are going to be passed (like the name for the port). Also, I'm planning to add an API within qemu for data transfer over serial ports and a key-value pair will be suitable for that. So that'll require a separate parameter as well. This API will be useful to support migration better and also qemu to converse with the guest. So extending the -serial option is certainly possible but I've to make sure the virtio serial-specific options don't apply to the others. I've not gotten to look into that yet. Amit