1. 19 6月, 2018 1 次提交
  2. 14 6月, 2018 1 次提交
  3. 12 6月, 2018 1 次提交
  4. 08 6月, 2018 3 次提交
  5. 06 6月, 2018 4 次提交
  6. 05 6月, 2018 5 次提交
  7. 31 5月, 2018 2 次提交
    • M
      testUpdateQEMUCaps: Don't leak host cpuData · 5276ec71
      Michal Privoznik 提交于
      When preparing qemuCaps for test cases the following is
      happening:
      
      qemuTestParseCapabilitiesArch() is called, which calls
      virQEMUCapsLoadCache() which in turn calls
      virQEMUCapsInitHostCPUModel() which sets qemuCaps->kvmCPU and
      qemuCaps->tcgCPU.
      
      But then the code tries to update the capabilities:
      
      testCompareXMLToArgv() calls testUpdateQEMUCaps() which calls
      virQEMUCapsInitHostCPUModel() again overwriting previously
      allocated memory. The solution is to free host cpuData in
      testUpdateQEMUCaps().
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      Reviewed-by: NJiri Denemark <jdenemar@redhat.com>
      5276ec71
    • M
      qemuxml2argvtest: Don't initialize qemuCaps twice · 879cff55
      Michal Privoznik 提交于
      There's no point in calling testInitQEMUCaps() (which sets
      info.qemuCaps) only to overwrite (and leak) it on the very next
      line.
      
      ==12962== 296 (208 direct, 88 indirect) bytes in 1 blocks are definitely lost in loss record 265 of 331
      ==12962==    at 0x4C2CF26: calloc (vg_replace_malloc.c:711)
      ==12962==    by 0x5D28D9F: virAllocVar (viralloc.c:560)
      ==12962==    by 0x5D96AB4: virObjectNew (virobject.c:239)
      ==12962==    by 0x56DB7C7: virQEMUCapsNew (qemu_capabilities.c:1480)
      ==12962==    by 0x112A5B: testInitQEMUCaps (qemuxml2argvtest.c:361)
      ==12962==    by 0x1371C8: mymain (qemuxml2argvtest.c:2871)
      ==12962==    by 0x13AD0B: virTestMain (testutils.c:1120)
      ==12962==    by 0x1372FD: main (qemuxml2argvtest.c:2883)
      
      Removing the function call renders @gic argument unused therefore
      it's removed from the macro (and all its callers).
      Signed-off-by: NMichal Privoznik <mprivozn@redhat.com>
      879cff55
  8. 29 5月, 2018 1 次提交
  9. 25 5月, 2018 1 次提交
  10. 23 5月, 2018 2 次提交
  11. 18 5月, 2018 1 次提交
  12. 16 5月, 2018 2 次提交
  13. 15 5月, 2018 1 次提交
  14. 14 5月, 2018 2 次提交
  15. 11 5月, 2018 2 次提交
  16. 07 5月, 2018 1 次提交
    • J
      Deprecate QEMU_CAPS_NO_KVM_PIT · 941c8b0d
      Ján Tomko 提交于
      The -no-kvm-pit-reinjection option has been deprecated since
      its introduction in QEMU 1.3. See commit <1569fa14>.
      
      Drop the capability since all the QEMUs we support allow tuning
      the kvm-pit properties via -global.
      
      Also add the QEMU_CAPS_KVM_PIT_TICK_POLICY to the clock-catchup
      tests, since expecting it to succeed with QEMU that does not
      have kvm-pit makes no sense.
      Signed-off-by: NJán Tomko <jtomko@redhat.com>
      Reviewed-by: NJohn Ferlan <jferlan@redhat.com>
      941c8b0d
  17. 04 5月, 2018 1 次提交
  18. 03 5月, 2018 1 次提交
  19. 23 4月, 2018 2 次提交
  20. 19 4月, 2018 3 次提交
  21. 17 4月, 2018 3 次提交