From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [PULL 0/9] valgrind/coverity/i386/s390x: memcheck false positives
Date: Thu, 20 Nov 2014 22:33:32 +0100 [thread overview]
Message-ID: <1416519221-22299-1-git-send-email-borntraeger@de.ibm.com> (raw)
Paolo, Peter,
here is an updated version of my valgrind tree. Please review and
consider for 2.3.
The following changes since commit af3ff19b48f0bbf3a8bd35c47460358e8c6ae5e5:
Update version for v2.2.0-rc2 release (2014-11-18 18:00:58 +0000)
are available in the git repository at:
git://github.com/borntraeger/qemu.git tags/memcheck
for you to fetch changes up to 113fb9793bf21a3219d305206c79024b0801d7ab:
coverity/s390x: avoid false positive in kvm_irqchip_add_adapter_route (2014-11-20 22:10:58 +0100)
----------------------------------------------------------------
valgrind/coverity/i386/s390x: memcheck false positives
Let's avoid most memcheck false positives in KVM ioctls.
----------------------------------------------------------------
Christian Borntraeger (9):
valgrind: avoid false positives in KVM_GET_DIRTY_LOG ioctl
valgrind/i386: avoid false positives on KVM_SET_CLOCK ioctl
valgrind/i386: avoid false positives on KVM_SET_PIT ioctl
valgrind/i386: avoid false positives on KVM_SET_XCRS ioctl
valgrind/i386: avoid false positives on KVM_SET_MSRS ioctl
valgrind/i386: avoid false positives on KVM_GET_MSRS ioctl
valgrind/i386: avoid false positives on KVM_SET_VCPU_EVENTS ioctl
valgrind/s390x: avoid false positives on KVM_SET_FPU ioctl
coverity/s390x: avoid false positive in kvm_irqchip_add_adapter_route
hw/i386/kvm/clock.c | 3 +--
hw/i386/kvm/i8254.c | 2 +-
kvm-all.c | 4 ++--
target-i386/kvm.c | 24 ++++++++++++++++++------
target-s390x/kvm.c | 2 +-
5 files changed, 23 insertions(+), 12 deletions(-)
next reply other threads:[~2014-11-20 21:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 21:33 Christian Borntraeger [this message]
2014-11-20 21:33 ` [Qemu-devel] [PULL 1/9] valgrind: avoid false positives in KVM_GET_DIRTY_LOG ioctl Christian Borntraeger
2014-11-20 21:33 ` [Qemu-devel] [PULL 2/9] valgrind/i386: avoid false positives on KVM_SET_CLOCK ioctl Christian Borntraeger
2014-11-20 21:33 ` [Qemu-devel] [PULL 3/9] valgrind/i386: avoid false positives on KVM_SET_PIT ioctl Christian Borntraeger
2014-11-20 21:33 ` [Qemu-devel] [PULL 4/9] valgrind/i386: avoid false positives on KVM_SET_XCRS ioctl Christian Borntraeger
2014-11-20 21:33 ` [Qemu-devel] [PULL 5/9] valgrind/i386: avoid false positives on KVM_SET_MSRS ioctl Christian Borntraeger
2014-11-20 21:33 ` [Qemu-devel] [PULL 6/9] valgrind/i386: avoid false positives on KVM_GET_MSRS ioctl Christian Borntraeger
2014-11-20 21:33 ` [Qemu-devel] [PULL 7/9] valgrind/i386: avoid false positives on KVM_SET_VCPU_EVENTS ioctl Christian Borntraeger
2014-11-20 21:33 ` [Qemu-devel] [PULL 8/9] valgrind/s390x: avoid false positives on KVM_SET_FPU ioctl Christian Borntraeger
2014-11-20 21:33 ` [Qemu-devel] [PULL 9/9] coverity/s390x: avoid false positive in kvm_irqchip_add_adapter_route Christian Borntraeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1416519221-22299-1-git-send-email-borntraeger@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).