From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Share Vmware communication port between devices
Date: Tue, 21 Aug 2007 13:38:29 -0500 [thread overview]
Message-ID: <1187721509.8368.1.camel@squirrel> (raw)
In-Reply-To: <20070821182314.2F3D95A172@smtp3-g19.free.fr>
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é
next prev parent reply other threads:[~2007-08-21 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-21 18:17 [Qemu-devel] [PATCH] Share Vmware communication port between devices Hervé Poussineau
2007-08-21 18:38 ` Anthony Liguori [this message]
2007-08-21 19:16 ` Thomas Frey
-- strict thread matches above, loose matches on Subject: below --
2007-08-21 20:10 Hervé Poussineau
2007-08-21 21:10 ` Anthony Liguori
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1187721509.8368.1.camel@squirrel \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).