From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id D9C5B591A for ; Tue, 19 Jan 2016 15:29:36 +0100 (CET) Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id C8393344EB2; Tue, 19 Jan 2016 14:29:35 +0000 (UTC) Received: from hmsreliant.think-freely.org (unused [10.10.52.177] (may be forged)) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u0JETVQb008169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 19 Jan 2016 09:29:34 -0500 Date: Tue, 19 Jan 2016 09:29:31 -0500 From: Neil Horman To: Thomas Monjalon Message-ID: <20160119142930.GA25388@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> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3759018.lgeOm8Q2D2@xps13> User-Agent: Mutt/1.5.24 (2015-08-30) X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26 Cc: dev@dpdk.org 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 14:29:37 -0000 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