public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Dimon Zhao <dimon.zhao@nebula-matrix.com>
Cc: dev@dpdk.org, Kyo Liu <kyo.liu@nebula-matrix.com>,
	Leon Yu <leon.yu@nebula-matrix.com>,
	Sam Chen <sam.chen@nebula-matrix.com>
Subject: Re: [PATCH v3 1/1] net/nbl: add igb uio support for NBL VF devices
Date: Wed, 25 Feb 2026 08:50:21 -0800	[thread overview]
Message-ID: <20260225085021.4182499e@phoenix.local> (raw)
In-Reply-To: <20260225033943.30751-2-dimon.zhao@nebula-matrix.com>

On Tue, 24 Feb 2026 19:39:42 -0800
Dimon Zhao <dimon.zhao@nebula-matrix.com> wrote:

> Due to a chip design limitation, only the VF
> supports the igb_uio driver. The PF does not.
> 
> The igb_uio driver requires allocating interrupts and configuring the
> PCIe MSI-X table before the driver's probe function is called.
> This pre-probe configuration is only possible on the VF due to the
> hardware limitation; the PF can only configure the MSI-X table during
> its probe process.
> 
> Therefore, using igb_uio on the PF will fail.
> This commit clarifies this restriction.
> 
> Signed-off-by: Dimon Zhao <dimon.zhao@nebula-matrix.com>
> ---
>  doc/guides/nics/nbl.rst                       | 11 ++++
>  doc/guides/rel_notes/release_26_03.rst        |  4 ++
>  drivers/net/nbl/nbl_core.c                    |  2 +
>  drivers/net/nbl/nbl_dev/nbl_dev.c             | 33 ++++++++++--
>  drivers/net/nbl/nbl_dev/nbl_dev.h             |  3 ++
>  drivers/net/nbl/nbl_dispatch.c                | 50 +++++++++++++++++++
>  drivers/net/nbl/nbl_ethdev.c                  | 13 +++++
>  .../nbl_hw/nbl_hw_leonis/nbl_hw_leonis_snic.c | 12 +++++
>  .../nbl_hw/nbl_hw_leonis/nbl_hw_leonis_snic.h |  9 ++++
>  .../nbl/nbl_hw/nbl_hw_leonis/nbl_res_leonis.c | 10 ++++
>  drivers/net/nbl/nbl_include/nbl_def_channel.h |  5 ++
>  .../net/nbl/nbl_include/nbl_def_dispatch.h    |  3 ++
>  drivers/net/nbl/nbl_include/nbl_def_hw.h      |  3 ++
>  .../net/nbl/nbl_include/nbl_def_resource.h    |  3 ++
>  14 files changed, 157 insertions(+), 4 deletions(-)
> 
> diff --git a/doc/guides/nics/nbl.rst b/doc/guides/nics/nbl.rst
> index ba0a119dfd..c74826a3c2 100644
> --- a/doc/guides/nics/nbl.rst
> +++ b/doc/guides/nics/nbl.rst
> @@ -101,3 +101,14 @@ Limitations or Known Issues
>  32-bit architectures are not supported.
>  
>  Windows and BSD are not supported yet.
> +
> +**igb_uio Driver Support**
> +
> +Due to chip design limitations, only the VF supports the ``igb_uio`` driver,
> +PF does not support this driver.
> +
> +**uio_pci_generic Driver Support**
> +
> +The ``uio_pci_generic`` driver is not supported on either PF or VF devices.
> +This is because the NBL PMD requires MSI-X interrupts to receive mailbox
> +messages, but the ``uio_pci_generic`` driver does not support MSI-X interrupts.

The igb_uio driver is deprecated at this point, it is not upstream and has
lots of issues. Can VFIO be used in no IOMMU mode for this instead?


  reply	other threads:[~2026-02-25 16:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  2:40 [PATCH v1 0/1] support igb uio driver for VF devices Dimon Zhao
2026-02-11  2:40 ` [PATCH v1 1/1] net/nbl: add igb_uio support for NBL " Dimon Zhao
2026-02-11 17:13   ` Stephen Hemminger
2026-02-13 14:54     ` 回复:[PATCH " Dimon
2026-02-13 11:21 ` [PATCH v2 0/1] support igb uio driver for " Dimon Zhao
2026-02-13 11:21   ` [PATCH v2 1/1] net/nbl: add igb uio support for NBL " Dimon Zhao
2026-02-13 19:59     ` Stephen Hemminger
2026-02-25  3:39 ` [PATCH v3 0/1] support igb uio driver for " Dimon Zhao
2026-02-25  3:39   ` [PATCH v3 1/1] net/nbl: add igb uio support for NBL " Dimon Zhao
2026-02-25 16:50     ` Stephen Hemminger [this message]
2026-02-27  1:45       ` 回复:[PATCH " Dimon
2026-02-26 20:14     ` [PATCH " Stephen Hemminger
2026-02-27  2:57 ` [PATCH v4 0/1] NBL add probe checks for unsupported UIO drivers Dimon Zhao
2026-02-27  2:57   ` [PATCH v4 1/1] net/nbl: " Dimon Zhao

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=20260225085021.4182499e@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=dimon.zhao@nebula-matrix.com \
    --cc=kyo.liu@nebula-matrix.com \
    --cc=leon.yu@nebula-matrix.com \
    --cc=sam.chen@nebula-matrix.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