From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.tuxdriver.com (charlotte.tuxdriver.com [70.61.120.58]) by dpdk.org (Postfix) with ESMTP id 9329E559C for ; Tue, 19 Jan 2016 21:56:27 +0100 (CET) Received: from hmsreliant.think-freely.org ([2001:470:8:a08:7aac:c0ff:fec2:933b] helo=localhost) by smtp.tuxdriver.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.63) (envelope-from ) id 1aLdK9-0004Dh-EJ; Tue, 19 Jan 2016 15:56:24 -0500 Date: Tue, 19 Jan 2016 15:56:14 -0500 From: Neil Horman To: Stephen Hemminger Message-ID: <20160119205614.GA24277@hmsreliant.think-freely.org> References: <1452430254-30390-1-git-send-email-david.marchand@6wind.com> <1453120248-28274-1-git-send-email-david.marchand@6wind.com> <1453120248-28274-11-git-send-email-david.marchand@6wind.com> <3759018.lgeOm8Q2D2@xps13> <20160119142930.GA25388@hmsreliant.think-freely.org> <20160119081019.607a9b48@xeon-e3> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20160119081019.607a9b48@xeon-e3> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Score: -1.0 (-) X-Spam-Status: No Cc: dev@dpdk.org, Neil Horman Subject: Re: [dpdk-dev] [PATCH v2 10/10] pci: place all uio pci device ids in a dedicated section X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2016 20:56:27 -0000 On Tue, Jan 19, 2016 at 08:10:19AM -0800, Stephen Hemminger wrote: > On Tue, 19 Jan 2016 09:29:31 -0500 > Neil Horman wrote: > > > On Tue, Jan 19, 2016 at 08:30:40AM +0100, Thomas Monjalon wrote: > > > 2016-01-18 13:30, David Marchand: > > > > We could do something à la modinfo, but let's keep it simple for now. > > > > > > > > With this, you can extract the devices that need to be bound to uio / vfio > > > > with tools like objdump : > > > > > > > > $ objdump -j rte_pci_id_uio -s build/lib/librte_pmd_fm10k.so > > > > > > > > Contents of section rte_pci_id_uio: > > > > 15760 8680a415 ffffffff 8680d015 ffffffff ................ > > > > 15770 8680a515 ffffffff 00000000 00000000 ................ > > > > > > Yes we need a modinfo-like tool. > > > Currently, the UIO/VFIO binding can be done after parsing the PCI device list. > > > It is better to define the device ids locally to their drivers but it must > > > be integrated with an appropriate parsing tool at the same time. > > > And more importantly than any tool, the format of these ELF data must be > > > properly defined, documented and extensible. > > > > > > Is there someone experimented with such format definition? > > > Stephen, you were asking for this change, what is your opinion? > > > I remember that Neil was also interested in this change: > > > http://dpdk.org/ml/archives/dev/2015-January/012115.html > > > Panu, Christian, this change could be related to distribution packaging. > > > Thanks for helping to move this change forward. > > > > Yes, I would be interested in seeing this. Is the ask here that someone do it? > > As I recall from the last thread that you reference, I thought David M was > > interested in writing it and soliciting for ideas. If thats no longer the case, > > I can take a stab at writing it. > > > > Neil > > > > If these are libraries is there a way to have a real entry point > to dump PCI id's. > Sure, you could write a method that could be dlsym-ed easily enough to fetch an array of pci ids, or just print stuff the console. Not sure thats the best way, but definately an option Neil