From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 0/9] valgrind/i386/s390x: memcheck false positives
Date: Thu, 13 Nov 2014 20:07:28 +0100 [thread overview]
Message-ID: <54650170.50000@de.ibm.com> (raw)
In-Reply-To: <5464C17A.2060303@redhat.com>
Am 13.11.2014 um 15:34 schrieb Paolo Bonzini:
> On 30/10/2014 10:36, Christian Borntraeger wrote:
>> This series avoids most memcheck false positives in KVM ioctls on s390x
>> and x86_64.
>>
>> Please review and consider for 2.2 or later. Some of these things could
>> also be fixed in valgrind, but it will take a while until these changes
>> hit a release or distros.
>>
>> The series is also available via signed tag:
>>
>> The following changes since commit 3e9418e160cd8901c83a3c88967158084f5b5c03:
>>
>> Revert "main-loop.c: Handle SIGINT, SIGHUP and SIGTERM synchronously" (2014-10-27 15:05:09 +0000)
>>
>> are available in the git repository at:
>>
>> git://github.com/borntraeger/qemu.git tags/memcheck
>>
>> for you to fetch changes up to e5bcf96f709e57a54188ffa6a988b6acb603df7a:
>>
>> valgrind/s390x: avoid false positives on KVM_SET_FPU ioctl (2014-10-30 10:08:49 +0100)
>>
>> ----------------------------------------------------------------
>> valgrind/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_SET_MSRS(TSC) 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
>>
>> hw/i386/kvm/clock.c | 3 +--
>> hw/i386/kvm/i8254.c | 2 +-
>> kvm-all.c | 2 +-
>> target-i386/kvm.c | 9 +++++----
>> target-s390x/kvm.c | 2 +-
>> 5 files changed, 9 insertions(+), 9 deletions(-)
>>
>>
>>
>
> Christian, when you respin can you add another one in
> kvm_irqchip_add_adapter_route? Coverity reports kroute.pad as
> uninitialized.
OK, will do. It will take probably some more days, but it will happen :-)
prev parent reply other threads:[~2014-11-13 19:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 9:36 [Qemu-devel] [PATCH 0/9] valgrind/i386/s390x: memcheck false positives Christian Borntraeger
2014-10-30 9:36 ` [Qemu-devel] [PATCH 1/9] valgrind: avoid false positives in KVM_GET_DIRTY_LOG ioctl Christian Borntraeger
2014-10-30 9:36 ` [Qemu-devel] [PATCH 2/9] valgrind/i386: avoid false positives on KVM_SET_CLOCK ioctl Christian Borntraeger
2014-10-30 9:36 ` [Qemu-devel] [PATCH 3/9] valgrind/i386: avoid false positives on KVM_SET_PIT ioctl Christian Borntraeger
2014-10-30 9:36 ` [Qemu-devel] [PATCH 4/9] valgrind/i386: avoid false positives on KVM_SET_XCRS ioctl Christian Borntraeger
2014-10-30 9:36 ` [Qemu-devel] [PATCH 5/9] valgrind/i386: avoid false positives on KVM_SET_MSRS ioctl Christian Borntraeger
2014-10-30 9:36 ` [Qemu-devel] [PATCH 6/9] valgrind/i386: avoid false positives on KVM_SET_MSRS(TSC) ioctl Christian Borntraeger
2014-10-30 9:36 ` [Qemu-devel] [PATCH 7/9] valgrind/i386: avoid false positives on KVM_GET_MSRS ioctl Christian Borntraeger
2014-11-05 10:33 ` Paolo Bonzini
2014-11-05 10:37 ` Paolo Bonzini
2014-10-30 9:36 ` [Qemu-devel] [PATCH 8/9] valgrind/i386: avoid false positives on KVM_SET_VCPU_EVENTS ioctl Christian Borntraeger
2014-10-30 9:36 ` [Qemu-devel] [PATCH 9/9] valgrind/s390x: avoid false positives on KVM_SET_FPU ioctl Christian Borntraeger
2014-10-30 9:46 ` [Qemu-devel] [PATCH 0/9] valgrind/i386/s390x: memcheck false positives Peter Maydell
2014-10-30 9:50 ` Christian Borntraeger
2014-10-30 9:58 ` Peter Maydell
2014-10-30 11:01 ` Christian Borntraeger
2014-10-30 13:03 ` Paolo Bonzini
2014-10-30 13:20 ` Christian Borntraeger
2014-11-03 12:27 ` Paolo Bonzini
2014-11-13 14:34 ` Paolo Bonzini
2014-11-13 19:07 ` Christian Borntraeger [this message]
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=54650170.50000@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).