From: Stephen Hemminger <stephen@networkplumber.org>
To: "11" <caowenbo@mucse.com>
Cc: <thomas@monjalon.net>, <dev@dpdk.org>, <ferruh.yigit@amd.com>,
<andrew.rybchenko@oktetlabs.ru>, <yaojun@mucse.com>
Subject: Re: [PATCH v13 00/28] [v13]drivers/net Add Support mucse N10 Pmd Driver
Date: Mon, 24 Feb 2025 12:18:57 -0800 [thread overview]
Message-ID: <20250224121857.22e51b36@hermes.local> (raw)
In-Reply-To: <7965B24DF5ABB77F+000101db8355$35272be0$9f7583a0$@mucse.com>
On Thu, 20 Feb 2025 13:06:30 +0800
"11" <caowenbo@mucse.com> wrote:
> Hi Stephen,
>
> For the release thing, that be ok.
>
> But for Debian 12 with MUSDK it be failed, do I need to fixed it ,
> The ability when I used it that I had been memset it. But the compile-tool
> is warning it,
> hw->phy_port_ids[idx] = ability.port_ids[idx];
>
> Branch: master
> CommitID:968f7b6d7b6a7e60e6e551db430c4eecaccbbfd2
>
> 151613-151639 --> testing issues
>
> Upstream job id: Generic-DPDK-Compile-Meson#362983
>
> Test environment and result as below:
>
> +----------------------------------------+--------------------+
> | Environment | dpdk_meson_compile |
> +========================================+====================+
> | RHEL9 (ARM) | PASS |
> +----------------------------------------+--------------------+
> | Ubuntu 20.04 ARM GCC Cross Compile | PASS |
> +----------------------------------------+--------------------+
> | Ubuntu 20.04 ARM SVE | PASS |
> +----------------------------------------+--------------------+
> | Debian 12 with MUSDK | FAIL |
> +----------------------------------------+--------------------+
> | Fedora 40 (ARM Clang) | PASS |
> +----------------------------------------+--------------------+
> | Fedora 41 (ARM Clang) | PASS |
> +----------------------------------------+--------------------+
> | Fedora 41 (ARM) | PASS |
> +----------------------------------------+--------------------+
> | Fedora 40 (ARM) | PASS |
> +----------------------------------------+--------------------+
> | Ubuntu 20.04 (ARM) | PASS |
> +----------------------------------------+--------------------+
> | Ubuntu 22.04 (ARM) | PASS |
> +----------------------------------------+--------------------+
> | Ubuntu 24.04 (ARM) | PASS |
> +----------------------------------------+--------------------+
> | CentOS Stream 9 (ARM) | PASS |
> +----------------------------------------+--------------------+
> | CentOS Stream 10 (ARM) | PASS |
> +----------------------------------------+--------------------+
> | Debian 11 (Buster) (ARM) | PASS |
> +----------------------------------------+--------------------+
> | Ubuntu 20.04 ARM Clang Cross Compile | PASS |
> +----------------------------------------+--------------------+
> | Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
> +----------------------------------------+--------------------+
> | Debian 12 (arm) | PASS |
> +----------------------------------------+--------------------+
>
> ==== 20 line log output for Debian 12 with MUSDK (dpdk_meson_compile): ====
> [888/1284] Linking static target drivers/libtmp_rte_net_r8169.a [889/1284]
> Generating rte_net_r8169.pmd.c with a custom command [890/1284] Compiling C
> object drivers/librte_net_r8169.a.p/meson-generated_.._rte_net_r8169.pmd.c.o
> [891/1284] Linking static target drivers/librte_net_r8169.a [892/1284]
> Compiling C object
> drivers/librte_net_r8169.so.25.1.p/meson-generated_.._rte_net_r8169.pmd.c.o
> [893/1284] Linking target drivers/librte_net_r8169.so.25.1 [894/1284]
> Compiling C object drivers/net/rnp/base/librnp_base.a.p/rnp_mbx.c.o
> [895/1284] Compiling C object
> drivers/net/rnp/base/librnp_base.a.p/rnp_fw_cmd.c.o
> [896/1284] Compiling C object
> drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o
> FAILED: drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o
> ccache aarch64-linux-gnu-gcc -Idrivers/net/rnp/base/librnp_base.a.p
> -Idrivers/net/rnp/base -I../drivers/net/rnp/base -I. -I.. -Iconfig
> -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include
> -I../lib/eal/linux/include -Ilib/eal/arm/include -I../lib/eal/arm/include
> -I../kernel/linux -Ilib/eal/common -I../lib/eal/common -Ilib/eal
> -I../lib/eal -Ilib/kvargs -I../lib/kvargs -Ilib/log -I../lib/log
> -Ilib/metrics -I../lib/metrics -Ilib/telemetry -I../lib/telemetry -Ilib/net
> -I../lib/net -Ilib/mbuf -I../lib/mbuf -Ilib/mempool -I../lib/mempool
> -Ilib/ring -I../lib/ring -Ilib/ethdev -I../lib/ethdev -Ilib/meter
> -I../lib/meter -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall
> -Winvalid-pch -Wextra -Werror -std=c11 -O3 -include rte_config.h -Wvla
> -Wcast-qual -Wdeprecated -Wformat -Wformat-nonliteral -Wformat-security
> -Wmissing-declarations -Wmissing-prototypes -Wnested-externs
> -Wold-style-definition -Wpointer-arith -Wsign-compare -Wstrict-prototypes
> -Wundef -Wwrite-st rings -Wno-packed-not-aligned
> -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -mcpu=cortex-a72
> -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation
> -Wno-address-of-packed-member -DRTE_LIBRTE_IXGBE_BYPASS -Wno-unused-value
> -Wno-unused-but-set-variable -Wno-unused-parameter -MD -MQ
> drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o -MF
> drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o.d -o
> drivers/net/rnp/base/librnp_base.a.p/rnp_mbx_fw.c.o -c
> ../drivers/net/rnp/base/rnp_mbx_fw.c
> ../drivers/net/rnp/base/rnp_mbx_fw.c: In function
> 'rnp_mbx_fw_get_capability':
> ../drivers/net/rnp/base/rnp_mbx_fw.c:257:65: error: 'ability' may be used
> uninitialized [-Werror=maybe-uninitialized]
> 257 | hw->phy_port_ids[idx] = ability.port_ids[idx];
> | ~~~~~~~~~~~~~~~~^~~~~
> ../drivers/net/rnp/base/rnp_mbx_fw.c:235:38: note: 'ability' declared here
> 235 | struct rnp_phy_abilities_rep ability;
> | ^~~~~~~
> cc1: all warnings being treated as errors
> ninja: build stopped: subcommand failed.
> ==== End log output ====
Yes, it looks like a compiler bug. Unfortunately, DPDK has to workaround
issues with buggy compilers
some times.
Maybe just do this instead
diff --git a/drivers/net/rnp/base/rnp_mbx_fw.c b/drivers/net/rnp/base/rnp_mbx_fw.c
index 4f351ce960..185bf4dee8 100644
--- a/drivers/net/rnp/base/rnp_mbx_fw.c
+++ b/drivers/net/rnp/base/rnp_mbx_fw.c
@@ -232,7 +232,7 @@ rnp_fw_get_phy_capability(struct rnp_eth_port *port,
int rnp_mbx_fw_get_capability(struct rnp_eth_port *port)
{
- struct rnp_phy_abilities_rep ability;
+ struct rnp_phy_abilities_rep ability = { };
struct rnp_hw *hw = port->hw;
u32 is_sgmii_bits = 0;
bool is_sgmii = false;
@@ -243,7 +243,6 @@ int rnp_mbx_fw_get_capability(struct rnp_eth_port *port)
u8 lane_idx;
u32 idx;
- memset(&ability, 0, sizeof(ability));
err = rnp_fw_get_phy_capability(port, &ability);
if (!err) {
hw->lane_mask = ability.lane_mask;
next prev parent reply other threads:[~2025-02-24 20:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 7:57 Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 01/28] net/rnp: add skeleton Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 02/28] net/rnp: add ethdev probe and remove Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 03/28] net/rnp: add log Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 04/28] net/rnp: support mailbox basic operate Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 05/28] net/rnp: add device init and uninit Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 06/28] net/rnp: add get device information operation Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 07/28] net/rnp: add support MAC promisc mode Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 08/28] net/rnp: add queue setup and release operations Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 09/28] net/rnp: add queue stop and start operations Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 10/28] net/rnp: add support device start stop operations Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 11/28] net/rnp: add RSS support operations Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 12/28] net/rnp: add support link update operations Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 13/28] net/rnp: add support link setup operations Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 14/28] net/rnp: add Rx burst simple support Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 15/28] net/rnp: add Tx " Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 16/28] net/rnp: add MTU set operation Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 17/28] net/rnp: add Rx scatter segment version Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 18/28] net/rnp: add Tx multiple " Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 19/28] net/rnp: add support basic stats operation Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 20/28] net/rnp: add support xstats operation Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 21/28] net/rnp: add unicast MAC filter operation Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 22/28] net/rnp: add supported packet types Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 23/28] net/rnp: add support Rx checksum offload Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 24/28] net/rnp: add support Tx TSO offload Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 25/28] net/rnp: support VLAN offloads Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 26/28] net/rnp: add support VLAN filters operations Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 27/28] net/rnp: add queue info operation Wenbo Cao
2025-02-19 7:57 ` [PATCH v13 28/28] net/rnp: support Rx/Tx burst mode info Wenbo Cao
2025-02-19 16:14 ` [PATCH v13 00/28] [v13]drivers/net Add Support mucse N10 Pmd Driver Stephen Hemminger
2025-02-20 5:06 ` 11
2025-02-24 20:18 ` Stephen Hemminger [this message]
2025-02-20 17:44 ` Stephen Hemminger
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=20250224121857.22e51b36@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=caowenbo@mucse.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=thomas@monjalon.net \
--cc=yaojun@mucse.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;
as well as URLs for NNTP newsgroup(s).