From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [4957] vmware backdoor interface fix (Chris Lalancette)
Date: Mon, 28 Jul 2008 18:58:03 +0000 [thread overview]
Message-ID: <E1KNXv1-00021G-43@cvs.savannah.gnu.org> (raw)
Revision: 4957
http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=4957
Author: aliguori
Date: 2008-07-28 18:58:02 +0000 (Mon, 28 Jul 2008)
Log Message:
-----------
vmware backdoor interface fix (Chris Lalancette)
VMWare backdoor interface should work with IN/OUT port ops, but
currently only IN is supported. BOCHS bios uses OUT to query UUID.
The patch adds OUT support.
Signed-off-by: Chris Lalancette <clalance@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Modified Paths:
--------------
trunk/hw/vmport.c
Modified: trunk/hw/vmport.c
===================================================================
--- trunk/hw/vmport.c 2008-07-28 18:55:32 UTC (rev 4956)
+++ trunk/hw/vmport.c 2008-07-28 18:58:02 UTC (rev 4957)
@@ -72,6 +72,13 @@
return s->func[command](s->opaque[command], addr);
}
+static void vmport_ioport_write(void *opaque, uint32_t addr, uint32_t val)
+{
+ CPUState *env = cpu_single_env;
+
+ env->regs[R_EAX] = vmport_ioport_read(opaque, addr);
+}
+
static uint32_t vmport_cmd_get_version(void *opaque, uint32_t addr)
{
CPUState *env = cpu_single_env;
@@ -89,6 +96,7 @@
void vmport_init(void)
{
register_ioport_read(0x5658, 1, 4, vmport_ioport_read, &port_state);
+ register_ioport_write(0x5658, 1, 4, vmport_ioport_write, &port_state);
/* Register some generic port commands */
vmport_register(VMPORT_CMD_GETVERSION, vmport_cmd_get_version, NULL);
reply other threads:[~2008-07-28 18:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1KNXv1-00021G-43@cvs.savannah.gnu.org \
--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).