From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: [PATCH] eal/devargs: add option to supply pci dev args Date: Tue, 5 Jun 2018 21:37:44 +0530 Message-ID: <20180605160742.GB6695@jerin> References: <20180605113128.15365-1-pbhagavatula@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: gaetan.rivet@6wind.com, thomas@monjalon.net, dev@dpdk.org To: Pavan Nikhilesh Return-path: Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0073.outbound.protection.outlook.com [104.47.34.73]) by dpdk.org (Postfix) with ESMTP id 412E61B638 for ; Tue, 5 Jun 2018 18:07:55 +0200 (CEST) Content-Disposition: inline In-Reply-To: <20180605113128.15365-1-pbhagavatula@caviumnetworks.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" -----Original Message----- > Date: Tue, 5 Jun 2018 17:01:28 +0530 > From: Pavan Nikhilesh > To: jerin.jacob@caviumnetworks.com, gaetan.rivet@6wind.com, > thomas@monjalon.net > Cc: dev@dpdk.org, Pavan Nikhilesh > Subject: [dpdk-dev] [PATCH] eal/devargs: add option to supply pci dev args > X-Mailer: git-send-email 2.17.1 > > Currently, the only way of supplying device argument to a pci device is > to whitelist it i.e. -w 000X:00:0X.0,self_test=1. This is not a very > feasible method as whitelisting a device has its own side effects. I think, it would good, if we describe the side effects. > > Add a new eal command line option --pci-args to pass device args without > the need to whitelist the devices. > > Signed-off-by: Pavan Nikhilesh > --- > lib/librte_eal/common/eal_common_devargs.c | 3 +++ > lib/librte_eal/common/eal_common_options.c | 7 +++++++ > lib/librte_eal/common/eal_options.h | 2 ++ > lib/librte_eal/common/include/rte_dev.h | 1 + > lib/librte_eal/common/include/rte_devargs.h | 1 + Missed to update the eal documentation.