[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-block] [PATCH 0/3] Reduce the number of Valgrind reports in un
From: |
Paolo Bonzini |
Subject: |
Re: [Qemu-block] [PATCH 0/3] Reduce the number of Valgrind reports in unit tests. |
Date: |
Tue, 13 Aug 2019 14:05:43 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 |
On 13/08/19 14:02, Andrey Shinkevich wrote:
> PINGING...
I thought I had already said I queued the series?
Paolo
> On 30/07/2019 19:01, Andrey Shinkevich wrote:
>> Running unit tests under the Valgrind may help to detect QEMU memory issues
>> (suggested by Denis V. Lunev). Some of the Valgrind reports relate to the
>> unit test code itself. Let's eliminate the detected memory issues to ease
>> locating critical ones.
>>
>> Andrey Shinkevich (3):
>> test-throttle: Fix uninitialized use of burst_length
>> tests: Fix uninitialized byte in test_visitor_in_fuzz
>> i386/kvm: initialize struct at full before ioctl call
>>
>> target/i386/kvm.c | 3 +++
>> tests/test-string-input-visitor.c | 8 +++-----
>> tests/test-throttle.c | 2 ++
>> 3 files changed, 8 insertions(+), 5 deletions(-)
>>
>