2016-05-24 15:41, Neil Horman: > Note that, in the case of dynamically linked applications, pmdinfo.py will > scan > for implicitly linked PMDs by searching the specified binaries .dynamic > section > for DT_NEEDED entries that contain the substring librte_pmd.
I don't know any DPDK app dynamically linked with a PMD (with DT_NEEDED). However it is a good idea to handle this case. But relying on the name assumption "librte_pmd" is really weak. > + $(Q)$(call rte_symlink, $(DESTDIR)$(datadir)/tools/pmdinfo.py, \ > + $(DESTDIR)$(bindir)/pmdinfo) I think we must prefix the tool name with dpdk. What about dpdk-objinfo or dpdk-pmdinfo? > +from elftools.elf.elffile import ELFFile > +from elftools.elf.dynamic import DynamicSection, DynamicSegment > +from elftools.elf.enums import ENUM_D_TAG > +from elftools.elf.segments import InterpSegment > +from elftools.elf.sections import SymbolTableSection Should it be possible to implement pmdinfogen with this Python library? I'll probably comment on the pmdinfo script details later. Just knowing you did a tool is enough to assert that it is a good step :) Thanks
