From: "Huang, ZhiminX" <zhiminx.huang@intel.com>
To: "Ye, MingjinX" <mingjinx.ye@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Yang, Qiming" <qiming.yang@intel.com>,
"Zhou, YidingX" <yidingx.zhou@intel.com>,
"Ye, MingjinX" <mingjinx.ye@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v4] app/test: append 'allow' parameters to secondary processes
Date: Fri, 13 Oct 2023 02:47:34 +0000 [thread overview]
Message-ID: <BN0PR11MB571295C6EAAE2DA788F7FAA9FDD2A@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230927034204.2279012-1-mingjinx.ye@intel.com>
> -----Original Message-----
> From: Mingjin Ye <mingjinx.ye@intel.com>
> Sent: Wednesday, September 27, 2023 11:42 AM
> To: dev@dpdk.org
> Cc: Yang, Qiming <qiming.yang@intel.com>; Zhou, YidingX
> <yidingx.zhou@intel.com>; Ye, MingjinX <mingjinx.ye@intel.com>;
> stable@dpdk.org
> Subject: [PATCH v4] app/test: append 'allow' parameters to secondary
> processes
>
> The 'allow' parameters are not passed to the secondary process, and all
> devices will be loaded by default. When the primary process specifies the
> 'allow' parameters and does not specify all devices that use the vfio-pci driver,
> the secondary process will not load the devices as expected, which will return
> incorrect test results.
>
> This patch fixes this issue by appending the 'allow' parameters to the
> secondary process.
>
> Fixes: 086eb64db39e ("test/pdump: add unit test for pdump library")
> Fixes: 148f963fb532 ("xen: core library changes")
> Fixes: af75078fece3 ("first public release")
> Fixes: b8d5e544e73e ("test: add procfs error message for multi-process
> launch")
> Cc: stable@dpdk.org
>
> Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
> ---
Verified multiple pcis with the '-a' parameter.
Tested-by: Zhimin Huang <zhiminx.huang@intel.com >
next prev parent reply other threads:[~2023-10-13 2:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 9:35 [PATCH] child process synchronization NIC startup parameters Kaisen You
2023-07-06 2:16 ` Yang, Qiming
2023-07-07 1:21 ` You, KaisenX
2023-07-06 19:07 ` Stephen Hemminger
2023-07-14 5:59 ` [PATCH v2] app/test:subprocess synchronization of parameters Kaisen You
2023-07-17 1:47 ` Kaisen You
2023-07-26 2:39 ` Kaisen You
2023-09-25 9:42 ` [PATCH v3] app/test: secondary process passes allow parameters Mingjin Ye
2023-09-25 9:58 ` David Marchand
2023-09-25 10:09 ` Ye, MingjinX
2023-09-25 10:19 ` David Marchand
2023-09-27 3:42 ` [PATCH v4] app/test: append 'allow' parameters to secondary processes Mingjin Ye
2023-10-13 2:47 ` Huang, ZhiminX [this message]
2023-11-09 11:13 ` Bruce Richardson
2023-11-10 10:30 ` [PATCH v5] app/test: secondary process passes allow parameters Mingjin Ye
2023-11-10 11:18 ` Bruce Richardson
2023-11-13 10:42 ` [PATCH v6] " Mingjin Ye
2023-11-13 11:11 ` Bruce Richardson
2023-11-14 10:28 ` [PATCH v7] " Mingjin Ye
2023-11-17 10:05 ` Huang, ZhiminX
2023-11-17 10:24 ` Ye, MingjinX
2023-11-17 11:17 ` Bruce Richardson
2023-11-24 10:28 ` Ye, MingjinX
2024-03-06 13:50 ` Thomas Monjalon
2024-10-03 16:00 ` [PATCH v2] app/test:subprocess synchronization of parameters Stephen Hemminger
2024-06-13 23:23 ` [PATCH] child process synchronization NIC startup parameters Stephen Hemminger
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=BN0PR11MB571295C6EAAE2DA788F7FAA9FDD2A@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=zhiminx.huang@intel.com \
--cc=dev@dpdk.org \
--cc=mingjinx.ye@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=yidingx.zhou@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).