On 03/09/2019 17:28, Kevin Wolf wrote:
> Am 03.09.2019 um 16:22 hat Andrey Shinkevich geschrieben:
>>
>>
>> On 03/09/2019 13:02, Kevin Wolf wrote:
>>> Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
In the current implementation of the QEMU bash iotests, only qemu-io
processes
Am 03.09.2019 um 16:22 hat Andrey Shinkevich geschrieben:
>
>
> On 03/09/2019 13:02, Kevin Wolf wrote:
> > Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
> >> In the current implementation of the QEMU bash iotests, only qemu-io
> >> processes may be run under the Valgrind with the swit
On 03/09/2019 13:02, Kevin Wolf wrote:
> Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
>> In the current implementation of the QEMU bash iotests, only qemu-io
>> processes may be run under the Valgrind with the switch '-valgrind'.
>> Let's allow the common.rc bash script running all o
On 03/09/2019 13:02, Kevin Wolf wrote:
> Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
>> In the current implementation of the QEMU bash iotests, only qemu-io
>> processes may be run under the Valgrind with the switch '-valgrind'.
>> Let's allow the common.rc bash script running all o
Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
> In the current implementation of the QEMU bash iotests, only qemu-io
> processes may be run under the Valgrind with the switch '-valgrind'.
> Let's allow the common.rc bash script running all other QEMU processes,
> such as qemu-kvm, qemu-
In the current implementation of the QEMU bash iotests, only qemu-io
processes may be run under the Valgrind with the switch '-valgrind'.
Let's allow the common.rc bash script running all other QEMU processes,
such as qemu-kvm, qemu-img, qemu-ndb and qemu-vxhs, under the Valgrind.
v7:
01: The co
