From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v7 13/15] eal: add hotplug add/remove functions Date: Fri, 30 Jun 2017 11:06:03 +0200 Message-ID: <2830134.KdhWyS32Ir@xps> References: <20170629182206.1072-1-jblunck@infradead.org> <20170629182206.1072-14-jblunck@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, gaetan.rivet@6wind.com, shreyansh.jain@nxp.com To: Jan Blunck Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 498E65689 for ; Fri, 30 Jun 2017 11:06:06 +0200 (CEST) In-Reply-To: <20170629182206.1072-14-jblunck@infradead.org> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 29/06/2017 20:22, Jan Blunck: > /** > + * Hotplug add a given device to a specific bus. > + * > + * @param busname > + * The bus name the device is added to. > + * @param devname > + * The device name. Based on this device name, eal will identify a driver > + * capable of handling it and pass it to the driver probing function. > + * @param devargs > + * Device arguments to be passed to the driver. > + * @return > + * 0 on success, negative on error. > + */ > +int rte_eal_hotplug_add(const char *busname, const char *devname, > + const char *devargs); After the hotplug, we may need to get the rte_device. Should we add a struct **rte_device as parameter, or should we add a helper function to get the rte_device from busname and devname?