1. 11 9月, 2012 14 次提交
  2. 10 9月, 2012 23 次提交
  3. 09 9月, 2012 2 次提交
    • J
      kvm: Clean up irqfd API · b131c74a
      Jan Kiszka 提交于
      No need to expose the fd-based interface, everyone will already be fine
      with the more handy EventNotifier variant. Rename the latter to clarify
      that we are still talking about irqfds here.
      Signed-off-by: NJan Kiszka <jan.kiszka@siemens.com>
      Acked-by: NAlex Williamson <alex.williamson@redhat.com>
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      b131c74a
    • C
      qemu: Use valgrind annotations to mark kvm guest memory as defined · 62fe8331
      Christian Borntraeger 提交于
      valgrind with kvm produces a big amount of false positives regarding
      "Conditional jump or move depends on uninitialised value(s)". This
      happens because the guest memory is allocated with qemu_vmalloc which
      boils down posix_memalign etc. This function is (correctly) considered
      by valgrind as returning undefined memory.
      
      Since valgrind is based on jitting code, it will not be able to see
      changes made by the guest to guest memory if this is done by KVM_RUN,
      thus keeping most of the guest memory undefined.
      
      Now lots of places in qemu will then use guest memory to change behaviour.
      To avoid the flood of these messages, lets declare the whole guest
      memory as defined. This will reduce the noise and allows us to see real
      problems.
      
      In the future we might want to make this conditional, since there
      is actually something that we can use those false positives for:
      These messages will point to code that depends on guest memory, so
      we can use these backtraces to actually make an audit that is focussed
      only at those code places. For normal development we dont want to
      see those messages, though.
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: NAvi Kivity <avi@redhat.com>
      62fe8331
  4. 08 9月, 2012 1 次提交