On 01/20/2010 10:46 AM, Avi Kivity wrote:
On 01/14/2010 04:20 PM, Avi Kivity wrote:
On 01/14/2010 04:06 PM, Dominik Brodowski wrote:
x/5i $eip
0x00007f317ab64a7b: movdqa %xmm0,(%rdi)
0x00007f317ab64a7f: movdqa %xmm0,0x10(%rdi)
0x00007f317ab64a84: movdqa %xmm0,0x20(%rdi)
0x00007f317ab64a89: movdqa %xmm0,0x30(%rdi)
0x00007f317ab64a8e: movdqa %xmm0,0x40(%rdi)
Same values for "vga vmware" and "vga std".
Yes - this has been reported. We need to start emulating movdqa and
a few of its friends.
So I have a nice patchset emulating this instruction (quite a pain,
since this is the first sse instruction we emulate), but it doesn't
help. The guest keeps using it so the display is incredibly slow.
Turns out the real problem is somewhere else - the guest is not
detecting VBE properly so it is forced to use the old slow vga
access. Not sure what the root cause is.
Is this with -vga std or -vga vmware? Is this a VESA driver in the guest?
Regards,
Anthony Liguori
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
