DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 1963] hotplug_mp: attach the share device failed in secondary processe
Date: Mon, 06 Jul 2026 06:48:17 +0000	[thread overview]
Message-ID: <bug-1963-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1963

            Bug ID: 1963
           Summary: hotplug_mp: attach the share device failed in
                    secondary processe
           Product: DPDK
           Version: 25.07
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: examples
          Assignee: dev@dpdk.org
          Reporter: yex.chen@intel.com
  Target Milestone: ---

Environment
===========
DPDK version: f77bc8767a952cf833fc9c85d6b5b8d77d39a5da 
version: 26.07.0-rc2
OS: Rhel9.6 (Plow)/5.14.0-570.12.1.el9_6.x86_64
Compiler: gcc version 11.5.0 20240719
Hardware platform: Intel(R) Xeon(R) 6767P
NIC hardware: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+
[8086:1583]
NIC firmware: 
  driver: vfio-pci
  kdriver: i40e-2.30.18
  firmware-version: 9.57 0x8001037b 1.4002.0

Test Setup
Steps to reproduce
==================
1. Build hotplug_mp   
CC=gcc meson -Dlibdir=lib --default-library=static x86_64-native-linuxapp-gcc
-Dmax_lcores=256    
ninja -C x86_64-native-linuxapp-gcc 
meson configure -Dexamples=multi_process/hotplug_mp x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc

2. bind pf to i40e 
usertools/dpdk-devbind.py --force --bind=i40e 0000:da:00.0 

3. Start dpdk-hotplug_mp as primary then secondary
x86_64-native-linuxapp-gcc/examples/dpdk-hotplug_mp  -l 1-2 -n 4 -a
0000:da:00.0 --proc-type=auto

4. Bind the port to vfio-pci
usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:da:00.0

5. Attach the physical device from primary, check primary and secondary
processes attach the share device
example> attach 0000:da:00.0     
example> list   

Results: 
========
the primary processe attach the share device successfully,
but the secondary processe attach the share device failed
example> list     
list all etherdev

Expected Result:
================
the primary and secondary processes attach the share device successfully
example> list      
list all etherdev      
0       0000:da:00.0


bad commit:
===========
commit: 1a2e26d8701d36c82fc2e405abb5e80d73df54bb

Author: David Marchand <david.marchand@redhat.com>
Date:   Wed Jun 24 14:07:56 2026 +0200

    dev: skip multi-process in hotplug

    If multi-process is disabled ({}no-shconf/{-}-in-memory),
    there is no need to build a multi-process message.

    Signed-off-by: David Marchand <david.marchand@redhat.com>
    Acked-by: Chengwen Feng <fengchengwen@huawei.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2026-07-06  6:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1963-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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