From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 1/3] drivers/bus: move driver assignment to end of probing Date: Thu, 11 Oct 2018 13:45:50 +0200 Message-ID: <2290243.n1gutIJ8el@xps> References: <20180907230958.21402-1-thomas@monjalon.net> <20181007220933.4533-2-thomas@monjalon.net> <21a07d94-44cc-9e99-1474-a13de77915ea@solarflare.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, gaetan.rivet@6wind.com, ophirmu@mellanox.com, qi.z.zhang@intel.com, ferruh.yigit@intel.com To: Andrew Rybchenko Return-path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 2B98E1B54B for ; Thu, 11 Oct 2018 13:45:53 +0200 (CEST) In-Reply-To: <21a07d94-44cc-9e99-1474-a13de77915ea@solarflare.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" 11/10/2018 12:53, Andrew Rybchenko: > On 10/8/18 1:09 AM, Thomas Monjalon wrote: > > The PCI mapping requires to know the PCI driver to use, > > even before the probing is done. That's why the PCI driver is > > referenced early inside the PCI device structure. See > > 1d20a073fa5e ("bus/pci: reference driver structure before mapping") > > > > However the rte_driver does not need to be referenced in rte_device > > before the device probing is done. > > By moving back this assignment at the end of the device probing, > > it becomes possible to make clear the status of a rte_device. > > > > Signed-off-by: Thomas Monjalon > > --- > > diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c > > index c7695d108..d63e68045 100644 > > --- a/drivers/bus/pci/pci_common.c > > +++ b/drivers/bus/pci/pci_common.c > > @@ -160,14 +160,12 @@ rte_pci_probe_one_driver(struct rte_pci_driver *dr, > > * driver flags for adjusting configuration. > > */ > > dev->driver = dr; > > - dev->device.driver = &dr->driver; > > It breaks net/sfc and I guess other drivers which use > rte_eth_dma_zone_reserve() > from probe. The function makes zone name using dev->device->driver->name. Please, can you show code line where we does such access? I checked such access before and did not find some. Anyway, it can be fixed by accessing rte_pci_driver->driver->name. Note that rte_pci_driver is referenced in rte_pci_device.