Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

体验新版 GitCode，发现更多精彩内容 >>

切换分支/标签
  1. 22 4月, 2009 1 次提交
  3. 19 4月, 2009 1 次提交
  5. 12 4月, 2009 1 次提交
  7. 11 4月, 2009 1 次提交
  9. 10 4月, 2009 1 次提交
  11. 08 4月, 2009 1 次提交
  13. 06 4月, 2009 1 次提交
  15. 29 3月, 2009 1 次提交
  17. 17 3月, 2009 1 次提交
  19. 13 3月, 2009 1 次提交
    • A
      Guest debugging support for KVM (Jan Kiszka) · e22a25c9
      由 aliguori 提交于 
      This is a backport of the guest debugging support for the KVM
accelerator that is now part of the KVM tree. It implements the reworked
KVM kernel API for guest debugging (KVM_CAP_SET_GUEST_DEBUG) which is
not yet part of any mainline kernel but will probably be 2.6.30 stuff.
So far supported is x86, but PPC is expected to catch up soon.

Core features are:
 - unlimited soft-breakpoints via code patching
 - hardware-assisted x86 breakpoints and watchpoints

Changes in this version:
 - use generic hook cpu_synchronize_state to transfer registers between
   user space and kvm
 - push kvm_sw_breakpoints into KVMState
Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>


git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6825 c046a42c-6fe2-441c-8c8c-71466251a162
      e22a25c9
  21. 08 3月, 2009 3 次提交
  23. 07 3月, 2009 3 次提交
  25. 23 2月, 2009 1 次提交
  27. 19 2月, 2009 1 次提交
    • A
      Fix cpu_physical_memory_rw() for 64-bit I/O accesses · 6c2934db
      由 aurel32 提交于 
      KVM uses cpu_physical_memory_rw() to access the I/O devices. When a
read or write with a length of 8-byte is requested, it is split into 2
4-byte accesses.

This has been broken in revision 5849. After this revision, only the
first 4 bytes are actually read/write to the device, as the target
address is changed, so on the next iteration of the loop the next 4
bytes are actually read/written elsewhere (in the RAM for the graphic
card).

This patch fixes screen corruption (and most probably data corruption)
with FreeBSD/amd64. Bug #2556746 in KVM bugzilla.
Signed-off-by: NAurelien Jarno <aurelien@aurel32.net>

git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@6628 c046a42c-6fe2-441c-8c8c-71466251a162
      6c2934db
  29. 11 2月, 2009 1 次提交
  31. 06 2月, 2009 1 次提交
  33. 27 1月, 2009 1 次提交
  35. 23 1月, 2009 2 次提交
  37. 16 1月, 2009 3 次提交
  39. 05 1月, 2009 1 次提交
  41. 29 12月, 2008 1 次提交
  43. 10 12月, 2008 1 次提交
    • A
      KVM: Coalesced MMIO support · f65ed4c1
      由 aliguori 提交于 
      MMIO exits are more expensive in KVM or Xen than in QEMU because they 
involve, at least, privilege transitions.  However, MMIO write 
operations can be effectively batched if those writes do not have side 
effects.

Good examples of this include VGA pixel operations when in a planar 
mode.  As it turns out, we can get a nice boost in other areas too.  
Laurent mentioned a 9.7% performance boost in iperf with the coalesced 
MMIO changes for the e1000 when he originally posted this work for KVM.
Signed-off-by: NAnthony Liguori <aliguori@us.ibm.com>



git-svn-id: svn://svn.savannah.nongnu.org/qemu/trunk@5961 c046a42c-6fe2-441c-8c8c-71466251a162
      f65ed4c1
  45. 09 12月, 2008 1 次提交
  47. 02 12月, 2008 2 次提交
  49. 01 12月, 2008 2 次提交
  51. 26 11月, 2008 1 次提交
  53. 25 11月, 2008 1 次提交
  55. 19 11月, 2008 4 次提交