From: "Jiale, SongX" <songx.jiale@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Ye, MingjinX" <mingjinx.ye@intel.com>
Subject: RE: [PATCH v4] test: fix option devices
Date: Thu, 17 Oct 2024 02:31:53 +0000 [thread overview]
Message-ID: <BN0PR11MB57439A830DF54B24B4C0B025E7472@BN0PR11MB5743.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20241016081719.1619975-1-mingjinx.ye@intel.com>
> -----Original Message-----
> From: Mingjin Ye <mingjinx.ye@intel.com>
> Sent: Wednesday, October 16, 2024 4:17 PM
> To: dev@dpdk.org
> Cc: Ye, MingjinX <mingjinx.ye@intel.com>; stable@dpdk.org
> Subject: [PATCH v4] test: fix option devices
>
> Without using allow (-a) or block (-b), EAL loads all devices by default.
> Unexpected devices may be loaded when running test cases in sub-processes.
>
> This patch fixes the issue by copying the parameters of the primary process if
> the allow (-a) or block (-b) option is not used when starting the child process.
>
> Also, EAL does not allow the options allow (-a) and block (-b) to be used at the
> same time.
>
> Fixes: b3ce7891ad38 ("test: fix probing in secondary process")
> Cc: stable@dpdk.org
>
> Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
> ---
Tested-by: Jiale Song <songx.jiale@intel.com>
prev parent reply other threads:[~2024-10-17 2:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 9:46 [PATCH] test: fix option block Mingjin Ye
2024-03-15 6:49 ` Jiale, SongX
[not found] ` <LV3PR11MB8601B4FC344CC7102C5AC010E5DD2@LV3PR11MB8601.namprd11.prod.outlook.com>
2024-07-03 14:35 ` Stokes, Ian
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
2024-10-07 17:02 ` Stephen Hemminger
2024-10-12 9:35 ` [PATCH v2] " Mingjin Ye
2024-10-12 22:20 ` Stephen Hemminger
2024-10-14 10:22 ` Ye, MingjinX
2024-10-14 10:00 ` [PATCH v3] test: fix option devices Mingjin Ye
2024-10-15 16:21 ` Stephen Hemminger
2024-10-16 8:17 ` [PATCH v4] " Mingjin Ye
2024-10-17 2:31 ` Jiale, SongX [this message]
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=BN0PR11MB57439A830DF54B24B4C0B025E7472@BN0PR11MB5743.namprd11.prod.outlook.com \
--to=songx.jiale@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).