From: Dave Airlie <airlied@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 3/6] Make sure to enable dirty log tracking for VMware VGA
Date: Fri, 18 Dec 2009 08:08:08 +1000 [thread overview]
Message-ID: <1261087691-8319-4-git-send-email-airlied@gmail.com> (raw)
In-Reply-To: <1261087691-8319-3-git-send-email-airlied@gmail.com>
From: Anthony Liguori <aliguori@us.ibm.com>
This is needed for VMware VGA to work properly under KVM.
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
---
hw/vmware_vga.c | 4 ++++
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/hw/vmware_vga.c b/hw/vmware_vga.c
index 07befc8..fcb6808 100644
--- a/hw/vmware_vga.c
+++ b/hw/vmware_vga.c
@@ -1169,6 +1169,10 @@ static void pci_vmsvga_map_mem(PCIDevice *pci_dev, int region_num,
#endif
cpu_register_physical_memory(s->vram_base, s->vga.vram_size,
iomemtype);
+
+ s->vga.map_addr = addr;
+ s->vga.map_end = addr + s->vga.vram_size;
+ vga_dirty_log_start(&s->vga);
}
static void pci_vmsvga_map_fifo(PCIDevice *pci_dev, int region_num,
--
1.6.5.2
next prev parent reply other threads:[~2009-12-17 22:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 22:08 [Qemu-devel] qemu fixup patch sequence Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 1/6] vmware: setup PCI BAR 2 for FIFO as per vmware spec Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 2/6] Make sure to enable dirty tracking of VBE vram mapping Dave Airlie
2009-12-17 22:08 ` Dave Airlie [this message]
2009-12-17 22:08 ` [Qemu-devel] [PATCH 4/6] Fix VMware VGA depth computation Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 5/6] VMware VGA: Only enable dirty log tracking when fifo is disabled Dave Airlie
2009-12-17 22:08 ` [Qemu-devel] [PATCH 6/6] vmware: increase cursor buffer size Dave Airlie
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=1261087691-8319-4-git-send-email-airlied@gmail.com \
--to=airlied@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.