DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matthew Hall <mhall@mhcomputing.net>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Debugging EAL PCI / Driver Init
Date: Sat, 2 Aug 2014 08:43:10 -0700	[thread overview]
Message-ID: <20140802154310.GA9104@mhcomputing.net> (raw)
In-Reply-To: <20140802152904.GA9064@mhcomputing.net>

Also, when using the separate libraries the problem still happens:

-lethdev -lrte_cfgfile -lrte_cmdline -lrte_distributor -lrte_hash 
-lrte_ip_frag -lrte_lpm -lrte_malloc -lrte_mbuf -lrte_mempool -lrte_pmd_e1000 
-lrte_pmd_pcap -lrte_pmd_virtio_uio -lrte_pmd_vmxnet3_uio -lrte_port 
-lrte_ring -lrte_table -lrte_timer -lrte_eal -lbsd -ldl -lpcap -lpthread

So it seems there is a special order or link technique which must be used, or 
rte_eal's PCI code won't be able to load the PMD's during PCI probing. Is it 
documented anywhere how to get that to work?

Thanks,
Matthew.

On Sat, Aug 02, 2014 at 08:29:04AM -0700, Matthew Hall wrote:
> I did a bit more experimentation and found the following. If I unmark the 
> rte_igb_pmd_init function as static, and call it directly from my code, the 
> driver will load, and the port count increments to 2:
> 
> EAL: PCI device 0000:01:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   PCI memory mapped at 0x7f09d45f2000
> EAL:   PCI memory mapped at 0x7f09d4730000
> PMD: eth_igb_dev_init(): port_id 0 vendorID=0x8086 deviceID=0x1521
> 
> EAL: PCI device 0000:01:00.1 on NUMA socket -1
> EAL:   probe driver: 8086:1521 rte_igb_pmd
> EAL:   PCI memory mapped at 0x7f09d0f00000
> EAL:   PCI memory mapped at 0x7f09d472c000
> PMD: eth_igb_dev_init(): port_id 1 vendorID=0x8086 deviceID=0x1521
> 
> So it seems like when you enable these options:
> 
> # Combine to one single library
> CONFIG_RTE_BUILD_COMBINE_LIBS=y
> CONFIG_RTE_LIBNAME="intel_dpdk"
> 
> You don't really get a working DPDK inside of "-lintel_dpdk". Someone 
> suggested linking with "-Xlinker -lintel_dpdk" but that didn't seem to help.
> 
> Is there a secret to getting a single integrated static library, where all of 
> the PMD's end up in the PCI driver list so rte_eal_pci_probe can find them? Or 
> some secret to linking against the combined library which works properly?
> 
> Matthew.
> 
> On Fri, Aug 01, 2014 at 10:51:38AM -0700, Matthew Hall wrote:
> > Hello,
> > 
> > I am running into a problem where Eth driver init works fine in a sample app 
> > and finds my NICs, and the NICs appear in rte_eal_pci_dump(stdout) but they 
> > don't show up in rte_eth_dev_count() even after rte_eal_pci_probe() is called 
> > the same as the sample apps, so my app won't boot.
> > 
> > I have a lot of experience using the older versions of the DPDK where you had 
> > to call the PMD init functions manually but no experience with the later 
> > versions where the DPDK is supposed to init the PMDs itself automatically.
> > 
> > What do I have to do to dump the most possible debug output on why the driver 
> > list for my PCI devices always seems empty? Any places I should look to see 
> > the issue? Maybe I didn't link it together with the right DPDK libs? I used 
> > the combined DPDK static lib libintel_dpdk.a to make things simpler as I had 
> > seen recommended in various places.
> > 
> > Thanks,
> > Matthew.

  reply	other threads:[~2014-08-02 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-01 17:51 Matthew Hall
2014-08-02 15:29 ` Matthew Hall
2014-08-02 15:43   ` Matthew Hall [this message]
     [not found]     ` <CAFLKUzKOPxC4jQBG6C07QXJ=MrcydxG9FdHD6h7omj6BY=99LQ@mail.gmail.com>
2014-08-02 16:46       ` Matthew Hall
2014-08-03 10:38         ` Alex Markuze
2014-08-03 11:41           ` Alex Markuze
2014-08-03 17:23             ` Matthew Hall
2014-08-03 18:13               ` Jayakumar, Muthurajan
2014-08-03 21:39                 ` Matthew Hall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140802154310.GA9104@mhcomputing.net \
    --to=mhall@mhcomputing.net \
    --cc=dev@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).