From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1INYci-0008HI-5N
	for qemu-devel@nongnu.org; Tue, 21 Aug 2007 14:38:40 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1INYcf-0008EH-0u
	for qemu-devel@nongnu.org; Tue, 21 Aug 2007 14:38:39 -0400
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1INYce-0008EE-RR
	for qemu-devel@nongnu.org; Tue, 21 Aug 2007 14:38:36 -0400
Received: from an-out-0708.google.com ([209.85.132.248])
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1INYcf-0000m2-9G
	for qemu-devel@nongnu.org; Tue, 21 Aug 2007 14:38:37 -0400
Received: by an-out-0708.google.com with SMTP id d11so212415and
	for <qemu-devel@nongnu.org>; Tue, 21 Aug 2007 11:38:34 -0700 (PDT)
Subject: Re: [Qemu-devel] [PATCH] Share Vmware communication port between
	devices
From: Anthony Liguori <anthony@codemonkey.ws>
In-Reply-To: <20070821182314.2F3D95A172@smtp3-g19.free.fr>
References: <20070821182314.2F3D95A172@smtp3-g19.free.fr>
Content-Type: text/plain; charset=utf-8
Date: Tue, 21 Aug 2007 13:38:29 -0500
Message-Id: <1187721509.8368.1.camel@squirrel>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Reply-To: qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org


On Tue, 2007-08-21 at 20:17 +0200, Hervé Poussineau wrote:
> Hi,
> 
> VMware registers the port 0x5658 to communicate between guest and host.
> At the moment, vmmouse.c is the only one to use this communication channel,
> so it registers the port. IMO, this design is not right because it will be
> hard to implement other functionalities of VMware.
> 
> I extracted non-mouse part from this file and created a framework for VMware
> communication in a new file. Devices can then register for specific
> commands, so communication port will be shared between devices.
> I also added support for "Get RAM size" command. More commands will be added
> later.

What other things are used for this port and where is it documented?
What is the "Get RAM size" command used by?

AFAIK, the vmware tools have a EULA that prevents them from being used
in QEMU guests.  Unless there's an open source driver that uses these
commands, I don't see the use of supporting them if the drivers are
restricted from being used within QEMU.

Regards,

Anthony Liguori

> Attached files:
> 0 - vmmouse-formatting.diff
> 	Replace tabs by 8 spaces. No code change
> 1 - adding-vmport.diff
> 	Add a generic framework for VMware communication port
> 2 - vmmouse-using-vmport.diff
> 	Use the framework for the VMware mouse emulation
> 
> Hervé