public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Marat Khalili <marat.khalili@huawei.com>
To: David Marchand <david.marchand@redhat.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "bruce.richardson@intel.com" <bruce.richardson@intel.com>
Subject: RE: [PATCH] test/eal: remove PCI probing for vdev tests
Date: Mon, 23 Feb 2026 17:16:17 +0000	[thread overview]
Message-ID: <8c67f4d90bd540e29c9e1ab4fcdc0dc8@huawei.com> (raw)
In-Reply-To: <20260223155603.3651641-1-david.marchand@redhat.com>

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Monday 23 February 2026 15:56
> To: dev@dpdk.org
> Cc: bruce.richardson@intel.com
> Subject: [PATCH] test/eal: remove PCI probing for vdev tests
> 
> Similarly to commit f67f76e6bbfd ("test/eal: remove PCI probing for
> recursive calls"), let's disable PCI probing in vdev tests as it
> triggers false positive failures in GHA.
> 
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
>  app/test/test_eal_flags.c | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/app/test/test_eal_flags.c b/app/test/test_eal_flags.c
> index bebddf1c98..06a605cce1 100644
> --- a/app/test/test_eal_flags.c
> +++ b/app/test/test_eal_flags.c
> @@ -422,17 +422,17 @@ test_invalid_vdev_flag(void)
> 
>  	/* Test with invalid vdev option */
>  	const char *vdevinval[] = {prgname, prefix, no_huge, eal_debug_logs,
> -				bus_debug_logs, vdev, "eth_dummy"};
> +				bus_debug_logs, no_pci, vdev, "eth_dummy"};
> 
>  	/* Test with valid vdev option */
>  	const char *vdevval1[] = {prgname, prefix, no_huge, eal_debug_logs,
> -				bus_debug_logs,	vdev, "net_ring0"};
> +				bus_debug_logs,	no_pci, vdev, "net_ring0"};

Could use this opportunity to replace tab before no_pci with space.

> 
>  	const char *vdevval2[] = {prgname, prefix, no_huge, eal_debug_logs,
> -				bus_debug_logs, vdev, "net_ring0,args=test"};
> +				bus_debug_logs, no_pci, vdev, "net_ring0,args=test"};
> 
>  	const char *vdevval3[] = {prgname, prefix, no_huge, eal_debug_logs,
> -				bus_debug_logs, vdev, "net_ring0,nodeaction=r1:0:CREATE"};
> +				bus_debug_logs, no_pci, vdev, "net_ring0,nodeaction=r1:0:CREATE"};
> 
>  	if (launch_proc(vdevinval) == 0) {
>  		printf("Error (line %d) - process did run ok with invalid vdev parameter\n",
> --
> 2.53.0

Acked-by: Marat Khalili <marat.khalili@huawei.com>
Tested-by: Marat Khalili <marat.khalili@huawei.com>

Definitely not a problem of this patch, but creating a separate define for each command-line argument like --no-huge does nothing to save us from repeating `prgname, prefix, eal_debug_logs, ...` bazillion times. If tokens are burning a hole in someone's pocket, perhaps instead we could move this whole command prefix into some kind of function or macro with parameters (possibly one launching subprocess as well).

Another thought, should we have NOPCI_OK/NOPCI_SKIP similar to ASAN and NOHUGE?

  parent reply	other threads:[~2026-02-23 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-23 15:56 [PATCH] test/eal: remove PCI probing for vdev tests David Marchand
2026-02-23 17:01 ` Bruce Richardson
2026-02-23 17:16 ` Marat Khalili [this message]
2026-02-24  7:48   ` David Marchand
2026-02-24  7:49 ` David Marchand

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=8c67f4d90bd540e29c9e1ab4fcdc0dc8@huawei.com \
    --to=marat.khalili@huawei.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    /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