public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: David Marchand <david.marchand@redhat.com>,
	Robin Jarry <rjarry@redhat.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Maxime Leroy <maxime@leroys.fr>,
	Kevin Traynor <ktraynor@redhat.com>, <dev@dpdk.org>
Subject: Re: [PATCH v3 0/7] Rework device probing
Date: Wed, 15 Apr 2026 11:05:50 +0100	[thread overview]
Message-ID: <ad9i_u8dhtierL-t@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35F657E3@smartserver.smartshare.dk>

On Mon, Apr 13, 2026 at 03:34:05PM +0200, Morten Brørup wrote:
> > From: David Marchand [mailto:david.marchand@redhat.com]
> > Sent: Saturday, 11 April 2026 12.11
> > 
> > On Fri, 10 Apr 2026 at 16:35, Morten Brørup <mb@smartsharesystems.com>
> > wrote:
> > >
> > > Is there a workaround until this patch is added, if I don't want
> > rte_eal_init() to probe any devices, but I want my application to probe
> > devices later by calling rte_bus_scan() followed by rte_bus_probe()?
> > >
> > > It's not something we really need, so if you don't know it off the
> > top of your head, don't spend time trying to figure it out.
> > 
> > Well, starting from the well known -a pci:0000:00:00.0 trick, I wrote
> > an incomplete workaround implemented for OVS.
> > https://patchwork.ozlabs.org/project/openvswitch/patch/20260226172429.2
> > 12034-3-david.marchand@redhat.com/
> > 
> > Incomplete, because some buses make life harder with some additional
> > parsing restraints (bus/dpaa is the first one that comes to mind) or
> > requiring a driver handling the device exists (bus/platform which has
> > *no* in-tree driver, though this is a different story..).
> 
> Thanks for all the input, David.
> 
> In my case it's only PCI bus devices, so I found a relatively simple workaround instead of using the "-a" trick.
> 
> I start by not binding the devices to the vfio-pci kernel driver.
> Then I call rte_eal_init(); and the devices are not detected by the EAL at this point.
> Then I bind the devices to the vfio-pci kernel driver.
> And finally I call rte_bus_scan() and rte_bus_probe(); then the devices are detected at this point.
> 
> Note: I have to pass "--iova-mode pa" to EAL init.
> Otherwise EAL init chooses VA mode, causing my drivers to not load, with the following message:
> "PCI_BUS:   Expecting 'PA' IOVA mode but current mode is 'VA', not initializing"
> 
> For anyone following the thread...
> 
> During experimentation, I observed that if the devices were bound to the vfio-pci kernel driver, and "-a ..." was passed to rte_eal_init() it did - as expected - not load the drivers.
> However, when calling rte_bus_scan() and rte_bus_probe() afterwards, the drivers were also not auto-detected at this point.
> I guess the "-a ..." parameter is sticky, which makes sense.
> 
Yes. The assumption is that, if you don't want to auto-probe, you want to
instead add the devices individually, device by device.

/Bruce

  reply	other threads:[~2026-04-15 10:06 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 10:52 [PATCH 0/8] Rework device probing David Marchand
2026-03-23 10:52 ` [PATCH 1/8] devtools: check packet forwarding in null test David Marchand
2026-03-23 10:52 ` [PATCH 2/8] bus/fslmc: fix bus cleanup David Marchand
2026-03-23 16:59   ` Kevin Traynor
2026-03-26  8:22     ` David Marchand
2026-03-26  8:49       ` Kevin Traynor
2026-03-24  5:15   ` Hemant Agrawal
2026-03-24  5:15   ` Hemant Agrawal
2026-03-23 10:52 ` [PATCH 3/8] drivers/bus: require probe function for NXP drivers David Marchand
2026-03-23 16:59   ` Kevin Traynor
2026-03-24  5:15   ` Hemant Agrawal
2026-03-23 10:52 ` [PATCH 4/8] drivers: cleanup devargs lookup in bus scan David Marchand
2026-03-24  5:16   ` Hemant Agrawal
2026-03-24 14:13   ` Kevin Traynor
2026-03-24 16:10   ` Stephen Hemminger
2026-03-23 10:52 ` [PATCH 5/8] bus: factorize devargs lookup David Marchand
2026-03-24 14:16   ` Kevin Traynor
2026-03-24 16:11   ` Stephen Hemminger
2026-03-23 10:53 ` [PATCH 6/8] bus: factorize device selection David Marchand
2026-03-24 14:15   ` Kevin Traynor
2026-03-26  8:48     ` David Marchand
2026-03-24 16:12   ` Stephen Hemminger
2026-03-23 10:53 ` [PATCH 7/8] bus: remove per bus scan mode David Marchand
2026-03-24 16:02   ` Kevin Traynor
2026-03-24 16:27     ` Kevin Traynor
2026-03-26  8:54     ` David Marchand
2026-03-23 10:53 ` [PATCH 8/8] eal: configure initial device probing David Marchand
2026-03-25 10:57   ` Kevin Traynor
2026-03-24  5:17 ` [PATCH 0/8] Rework " Hemant Agrawal
2026-03-25 15:22 ` Maxime Leroy
2026-03-26 10:24 ` [PATCH v2 0/7] " David Marchand
2026-03-26 10:24   ` [PATCH v2 1/7] devtools: check packet forwarding in null test David Marchand
2026-03-26 10:24   ` [PATCH v2 2/7] bus/fslmc: fix bus cleanup David Marchand
2026-03-26 11:50     ` Kevin Traynor
2026-03-26 10:24   ` [PATCH v2 3/7] drivers/bus: require probe function for NXP drivers David Marchand
2026-03-26 10:24   ` [PATCH v2 4/7] drivers: cleanup devargs lookup in bus scan David Marchand
2026-03-28  3:13     ` fengchengwen
2026-03-26 10:24   ` [PATCH v2 5/7] bus: factorize devargs lookup David Marchand
2026-03-26 11:51     ` Kevin Traynor
2026-03-28  3:33     ` fengchengwen
2026-04-03 14:22       ` David Marchand
2026-03-26 10:24   ` [PATCH v2 6/7] bus: factorize device selection David Marchand
2026-03-26 11:52     ` Kevin Traynor
2026-03-28  3:38     ` fengchengwen
2026-03-26 10:24   ` [PATCH v2 7/7] eal: configure initial device probing David Marchand
2026-03-28  4:00     ` fengchengwen
2026-04-03 14:25       ` David Marchand
2026-04-07 11:52 ` [PATCH v3 0/7] Rework " David Marchand
2026-04-07 11:52   ` [PATCH v3 1/7] devtools: check packet forwarding in null test David Marchand
2026-04-07 11:52   ` [PATCH v3 2/7] bus/fslmc: fix bus cleanup David Marchand
2026-04-07 11:52   ` [PATCH v3 3/7] drivers/bus: require probe function for NXP drivers David Marchand
2026-04-07 11:52   ` [PATCH v3 4/7] drivers/bus: cleanup devargs lookup in scan David Marchand
2026-04-07 11:52   ` [PATCH v3 5/7] bus: factorize devargs lookup David Marchand
2026-04-08  1:18     ` fengchengwen
2026-04-13 19:18     ` Thomas Monjalon
2026-04-13 19:48       ` Thomas Monjalon
2026-04-14 10:26         ` Thomas Monjalon
2026-04-14 10:43       ` David Marchand
2026-04-07 11:52   ` [PATCH v3 6/7] bus: factorize device selection David Marchand
2026-04-13 19:30     ` Thomas Monjalon
2026-04-15  9:53       ` Bruce Richardson
2026-04-07 11:52   ` [PATCH v3 7/7] eal: configure initial device probing David Marchand
2026-04-08  1:44     ` fengchengwen
2026-04-13 20:35     ` Thomas Monjalon
2026-04-07 11:58   ` [PATCH v3 0/7] Rework " David Marchand
2026-04-07 15:12   ` Stephen Hemminger
2026-04-10 14:34   ` Morten Brørup
2026-04-10 15:16     ` Kevin Traynor
2026-04-10 17:37     ` Stephen Hemminger
2026-04-10 21:13       ` [EXTERNAL] " Long Li
2026-04-10 22:50         ` Stephen Hemminger
2026-04-11  7:30         ` Morten Brørup
2026-04-11 10:10     ` David Marchand
2026-04-11 10:23       ` David Marchand
2026-04-13 13:34       ` Morten Brørup
2026-04-15 10:05         ` Bruce Richardson [this message]
2026-04-14 12:38 ` [PATCH v4 " David Marchand
2026-04-14 12:38   ` [PATCH v4 1/7] devtools: check packet forwarding in null test David Marchand
2026-04-14 12:38   ` [PATCH v4 2/7] bus/fslmc: fix bus cleanup David Marchand
2026-04-14 12:38   ` [PATCH v4 3/7] drivers/bus: require probe function for NXP drivers David Marchand
2026-04-14 12:38   ` [PATCH v4 4/7] drivers/bus: cleanup devargs lookup in scan David Marchand
2026-04-14 12:38   ` [PATCH v4 5/7] bus: factorize devargs lookup David Marchand
2026-04-14 12:38   ` [PATCH v4 6/7] bus: factorize device selection David Marchand
2026-04-14 12:38   ` [PATCH v4 7/7] eal: configure initial device probing David Marchand
2026-04-14 14:45     ` Thomas Monjalon
2026-04-15  7:07   ` [PATCH v4 0/7] Rework " David Marchand

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=ad9i_u8dhtierL-t@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=ktraynor@redhat.com \
    --cc=maxime@leroys.fr \
    --cc=mb@smartsharesystems.com \
    --cc=rjarry@redhat.com \
    /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