DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Stokes, Ian" <ian.stokes@intel.com>
To: "Ye, MingjinX" <mingjinx.ye@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: [PATCH] test: fix option block
Date: Wed, 3 Jul 2024 14:35:09 +0000	[thread overview]
Message-ID: <MW6PR11MB8309715865F6C2E86082AF3F92DD2@MW6PR11MB8309.namprd11.prod.outlook.com> (raw)
In-Reply-To: <LV3PR11MB8601B4FC344CC7102C5AC010E5DD2@LV3PR11MB8601.namprd11.prod.outlook.com>

> > The options allow (-a) and block (-b) cannot be used at the same time.
> > Therefore, allow (-a) will not be added when block (-b) is present.
> >
> > Fixes: b3ce7891ad38 ("test: fix probing in secondary process")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>

Hi Mingjin, in general the patch looks ok to me.

A general question of the behaviour of block and allow, is it always the case that the two are not allowed to be used side by side?
I had a look through the EAL documentation and didn't see and mention of this behaviour, but maybe I missed it?

Thanks
ian
> > ---
> >  app/test/process.h | 17 ++++++++++++++---
> >  1 file changed, 14 insertions(+), 3 deletions(-)
> >
> > diff --git a/app/test/process.h b/app/test/process.h index
> > 9fb2bf481c..388c7975cd 100644
> > --- a/app/test/process.h
> > +++ b/app/test/process.h
> > @@ -44,7 +44,7 @@ add_parameter_allow(char **argv, int max_capacity)
> >  	int count = 0;
> >
> >  	RTE_EAL_DEVARGS_FOREACH(NULL, devargs) {
> > -		if (strlen(devargs->name) == 0)
> > +		if (strlen(devargs->name) == 0 || devargs->type !=
> > +RTE_DEVTYPE_ALLOWED)
> >  			continue;
> >
> >  		if (devargs->data == NULL || strlen(devargs->data) == 0)
> > { @@ -74,7 +74,7 @@ process_dup(const char *const argv[], int numargs,
> > const char *env_value)  {
> >  	int num = 0;
> >  	char **argv_cpy;
> > -	int allow_num;
> > +	int allow_num, block_num;
> >  	int argv_num;
> >  	int i, status;
> >  	char path[32];
> > @@ -89,7 +89,18 @@ process_dup(const char *const argv[], int numargs,
> > const char *env_value)
> >  	if (pid < 0)
> >  		return -1;
> >  	else if (pid == 0) {
> > -		allow_num =
> > rte_devargs_type_count(RTE_DEVTYPE_ALLOWED);
> > +		allow_num = 0;
> > +		block_num = 0;
> > +
> > +		/* If block (-b) is present, allow (-a) is not added. */
> > +		for (i = 0; i < numargs; i++) {
> > +			if (strcmp(argv[i], "-b") == 0 ||
> > +			    strcmp(argv[i], "-block") == 0)
> > +				block_num++;
> > +		}
> > +		if (!block_num)
> > +			allow_num =
> > rte_devargs_type_count(RTE_DEVTYPE_ALLOWED);
> > +
> >  		argv_num = numargs + allow_num + 1;
> >  		argv_cpy = calloc(argv_num, sizeof(char *));
> >  		if (!argv_cpy)
> > --
> > 2.25.1


  parent reply	other threads:[~2024-07-03 14:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14  9:46 Mingjin Ye
2024-03-15  6:49 ` Jiale, SongX
     [not found] ` <LV3PR11MB8601B4FC344CC7102C5AC010E5DD2@LV3PR11MB8601.namprd11.prod.outlook.com>
2024-07-03 14:35   ` Stokes, Ian [this message]
2024-07-04  8:09     ` Ye, MingjinX
2024-07-04 12:02       ` Stokes, Ian
2024-07-05  1:38         ` Ye, MingjinX
2024-07-10  9:02           ` Stokes, Ian

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=MW6PR11MB8309715865F6C2E86082AF3F92DD2@MW6PR11MB8309.namprd11.prod.outlook.com \
    --to=ian.stokes@intel.com \
    --cc=dev@dpdk.org \
    --cc=mingjinx.ye@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).