Skip to content

Q
qemu

openeuler / qemu

通知 10
Star 0
Fork 0
Q
qemu

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

切换分支/标签
  1. 06 3月, 2019 1 次提交
  3. 05 2月, 2019 1 次提交
  5. 22 1月, 2019 1 次提交
  7. 10 1月, 2019 1 次提交
  9. 07 1月, 2019 16 次提交
  11. 20 12月, 2018 1 次提交
    • P
      intel_iommu: dma read/write draining support · ccc23bb0
      由 Peter Xu 提交于 
      Support DMA read/write draining should be easy for existing VT-d
emulation since the emulation itself does not have any request queue
there so we don't need to do anything to flush the un-commited queue.
What we need to do is to declare the support.

These capabilities are required to pass Windows SVVP test program.  It
is verified that when with parameters "x-aw-bits=48,caching-mode=off"
we can pass the Windows SVVP test with this patch applied.  Otherwise
we'll fail with:

        IOMMU[0] - DWD (DMA write draining) not supported
        IOMMU[0] - DWD (DMA read draining) not supported
        Segment 0 has no DMA remapping capable IOMMU units

However since these bits are not declared support for QEMU<=3.1, we'll
need a compatibility bit for it and we turn this on by default only
for QEMU>=4.0.

Please refer to VT-d spec 6.5.4 for more information.

CC: Yu Wang <wyu@redhat.com>
Fixes: https://bugzilla.redhat.com/show_bug.cgi?id=1654550Signed-off-by: NPeter Xu <peterx@redhat.com>
Reviewed-by: NMichael S. Tsirkin <mst@redhat.com>
Signed-off-by: NMichael S. Tsirkin <mst@redhat.com>
      ccc23bb0
  13. 12 12月, 2018 2 次提交
  15. 31 10月, 2018 1 次提交
  17. 19 10月, 2018 1 次提交
    • R
      hyperv: only add SynIC in compatible configurations · 9b4cf107
      由 Roman Kagan 提交于 
      Certain configurations do not allow SynIC to be used in QEMU.  In
particular,

- when hyperv_vpindex is off, SINT routes can't be used as they refer to
  the destination vCPU by vp_index

- older KVM (which doesn't expose KVM_CAP_HYPERV_SYNIC2) zeroes out
  SynIC message and event pages on every msr load, breaking migration

OTOH in-KVM users of SynIC -- SynIC timers -- do work in those
configurations, and we shouldn't stop the guest from using them.

To cover both scenarios, introduce an X86CPU property that makes CPU
init code to skip creation of the SynIC object (and thus disables any
SynIC use in QEMU) but keeps the KVM part of the SynIC working.
The property is clear by default but is set via compat logic for older
machine types.

As a result, when hv_synic and a modern machine type are specified, QEMU
will refuse to run unless vp_index is on and the kernel is recent
enough.  OTOH with an older machine type QEMU will run fine with
hv_synic=on against an older kernel and/or without vp_index enabled but
will disallow the in-QEMU uses of SynIC (in e.g. VMBus).
Signed-off-by: NRoman Kagan <rkagan@virtuozzo.com>
Message-Id: <20180921082217.29481-4-rkagan@virtuozzo.com>
Signed-off-by: NPaolo Bonzini <pbonzini@redhat.com>
      9b4cf107
  19. 30 7月, 2018 1 次提交
  21. 10 7月, 2018 1 次提交
  23. 29 6月, 2018 1 次提交
  25. 23 6月, 2018 1 次提交
  27. 12 6月, 2018 1 次提交
  29. 02 6月, 2018 1 次提交
  31. 15 5月, 2018 2 次提交
  33. 11 5月, 2018 1 次提交
  35. 07 5月, 2018 2 次提交
  37. 17 3月, 2018 1 次提交
  39. 12 3月, 2018 3 次提交