[dpdk-dev] Got bug while using valgrind on OVS-DPDK?

Sam batmanustc at gmail.com
Tue Apr 3 09:10:22 CEST 2018


Hi all,

solved by remove these:

-ifneq ($(filter $(AUTO_CPUFLAGS),__AVX__),)-CPUFLAGS +=
AVX-endif--ifneq ($(filter $(AUTO_CPUFLAGS),__RDRND__),)-CPUFLAGS +=
RDRAND-endif--ifneq ($(filter
$(AUTO_CPUFLAGS),__FSGSBASE__),)-CPUFLAGS += FSGSBASE-endif--ifneq
($(filter $(AUTO_CPUFLAGS),__F16C__),)-CPUFLAGS += F16C-endif--ifneq
($(filter $(AUTO_CPUFLAGS),__AVX2__),)-CPUFLAGS += AVX2-endif-



2018-04-03 14:45 GMT+08:00 Sam <batmanustc at gmail.com>:

> Hi all,
>
> I want to use valgrind to check if there is memleak of OVS-DPDK's
> ovs-vswitchd, so I use this command:
>
> valgrind ovs-vswitchd ...
>
>
> But got errors like this:
>
> the system does not support "RDRNAD"
>> please check that RTE_MACHINE is set correctly
>
>
> Does that mean valgrind does NOT support OVS-DPDK ovs-vswitchd? How could
> I check if ovs-vswitchd has no memleak?
>
> thank you~
>


More information about the dev mailing list