From: Olivier MATZ <olivier.matz@6wind.com>
To: Pablo de Lara <pablox.de.lara.guarch@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] app/test: Removed vdev test in EAL flags unit test
Date: Tue, 01 Jul 2014 10:31:29 +0200 [thread overview]
Message-ID: <53B271E1.1010304@6wind.com> (raw)
In-Reply-To: <1404139377-24580-1-git-send-email-pablox.de.lara.guarch@intel.com>
Hi Pablo,
On 06/30/2014 04:42 PM, Pablo de Lara wrote:
> From: Pablo de Lara <pablo.de.lara.guarch@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@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
next prev parent reply other threads:[~2014-07-01 8:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 14:42 Pablo de Lara
2014-07-01 8:31 ` Olivier MATZ [this message]
2014-07-01 8:32 ` [dpdk-dev] [PATCH] app/test: fix vdev test in test_eal_flags Olivier Matz
2014-07-01 8:59 ` [dpdk-dev] [PATCH] app/test: Removed vdev test in EAL flags unit test De Lara Guarch, Pablo
2014-07-01 9:20 ` Olivier MATZ
2014-07-01 9:21 ` [dpdk-dev] [PATCH v2] app/test: fix vdev test in test_eal_flags Olivier Matz
2014-07-01 11:44 ` De Lara Guarch, Pablo
2014-07-01 12:00 ` Olivier MATZ
2014-07-01 12:11 ` De Lara Guarch, Pablo
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=53B271E1.1010304@6wind.com \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=pablox.de.lara.guarch@intel.com \
/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).