[dpdk-dev] [PATCH v2 10/10] pci: place all uio pci device ids in a dedicated section

Neil Horman nhorman at redhat.com
Tue Jan 19 15:29:31 CET 2016

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.


More information about the dev mailing list