kvm/valgrind: don't mark memory as initialized

since commit 7dda5dc82a ("migration: initialize RAM to zero") the
guest memory is defined zero. No need to call valgrind on guest memory.
This reverts commit 62fe83318d ("qemu: Use valgrind annotations to
mark kvm guest memory as defined") thus speeding up kvm start if
<includedir>/valgrind/valgrind.h is available.

Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
This commit is contained in:
Christian Borntraeger 2014-09-25 21:07:54 +02:00 committed by Paolo Bonzini
parent a697d240ff
commit 541be9274e
2 changed files with 1 additions and 9 deletions

3
configure vendored
View file

@ -3961,12 +3961,11 @@ else
fi
########################################
# check if we have valgrind/valgrind.h and valgrind/memcheck.h
# check if we have valgrind/valgrind.h
valgrind_h=no
cat > $TMPC << EOF
#include <valgrind/valgrind.h>
#include <valgrind/memcheck.h>
int main(void) {
return 0;
}