Hi Olivier, > -----Original Message----- > From: Olivier MATZ [mailto:olivier.matz at 6wind.com] > Sent: Tuesday, July 01, 2014 9:31 AM > To: De Lara Guarch, Pablo; dev at dpdk.org > Cc: Olivier MATZ > Subject: Re: [dpdk-dev] [PATCH] app/test: Removed vdev test in EAL flags > unit test > > Hi Pablo, > > On 06/30/2014 04:42 PM, Pablo de Lara wrote: > > From: Pablo de Lara <pablo.de.lara.guarch at intel.com> > > > > In whitelist test, within EAL flags unit test, vdev flag > > was being tested, but test fails, as a secondary process > > cannot allocate memzones, so it cannot create the device > > and application exits. Also, this can be tested in ring > > pmd test, which needs vdev and not in whitelist, which > > should only test --pci-whitelist. > > > > Patch "app/test: fix build switches to enable cmdline tests" > > from Thomas Monjalon is needed for this patch. > > > > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch at intel.com> > > If the test cannot success because it is started from a secondary > process, do you think it is possible to do it with a primary process? > > I did a quick test and it works (see my patch in the same thread), but > as I'm not really familiar with this part of the code, I may have > forgotten something. > > Regards, > Olivier
I checked your patch, and I got this: ... EAL: Detected lcore 38 as core 11 on socket 1 EAL: Detected lcore 39 as core 12 on socket 1 EAL: Support maximum 64 logical core(s) by configuration. EAL: Detected 40 lcore(s) ./x86_64-native-linuxapp-gcc/app/test: unrecognized option '--prefix=whitelist' Also, I thought we could not run two primary process at the same time (considering that the test app is a primary process). Thanks, Pablo
