From: qemudev@loongson.cn
To: test-report@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>, zhoumin@loongson.cn
Subject: |FAILURE| pw148585-148587 [PATCH 3/3] net/bnxt: set max VFs count for P7
Date: Tue, 19 Nov 2024 01:04:51 +0800 [thread overview]
Message-ID: <202411181704.4AIH4prA2350866@localhost.localdomain> (raw)
In-Reply-To: <20241118173613.94224-4-ajit.khaparde@broadcom.com>
Test-Label: loongarch-compilation
Test-Status: FAILURE
http://dpdk.org/patch/148587
_ninja build failure_
Submitter: Ajit Khaparde <ajit.khaparde@broadcom.com>
Date: Mon, 18 Nov 2024 09:36:11 -0800
DPDK git baseline: Repo:dpdk-next-net-brcm
Branch: for-next-net
CommitID: 07e3bebf3c93750c52ed9be87edd212fbc22da0a
148585-148587 --> ninja build failed
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | FAIL |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
Ninja build logs:
-------------------------------BEGIN LOGS----------------------------
FAILED: drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_vnic.c.o
cc -Idrivers/libtmp_rte_net_bnxt.a.p -Idrivers -I../drivers -Idrivers/net/bnxt -I../drivers/net/bnxt -Idrivers/net/bnxt/tf_ulp -I../drivers/net/bnxt/tf_ulp -Idrivers/net/bnxt/tf_ulp/generic_templates -I../drivers/net/bnxt/tf_ulp/generic_templates -Idrivers/net/bnxt/tf_core -I../drivers/net/bnxt/tf_core -Idrivers/net/bnxt/tf_core/v3 -I../drivers/net/bnxt/tf_core/v3 -Idrivers/net/bnxt/hcapi/cfa -I../drivers/net/bnxt/hcapi/cfa -Idrivers/net/bnxt/hcapi/cfa_v3 -I../drivers/net/bnxt/hcapi/cfa_v3 -I../drivers/net/bnxt/hcapi/cfa_v3/include -I../drivers/net/bnxt/hcapi/cfa_v3/include/platform/dpdk -I../drivers/net/bnxt/hcapi/cfa_v3/bld/p70 -I../drivers/net/bnxt/hcapi/cfa_v3/bld/p70/host -I../drivers/net/bnxt/hcapi/cfa_v3/bld/include -I../drivers/net/bnxt/hcapi/cfa_v3/bld/include/host -I../drivers/net/bnxt/hcapi/cfa_v3/bld/include/p70 -I../drivers/net/bnxt/hcapi/cfa_v3/mm/include -I../drivers/net/bnxt/hcapi/cfa_v3/tim/include -I../drivers/net/bnxt/hcapi/cfa_v3/tpm/include -Ilib/ethdev -I../lib/
ethdev -I. -I.. -Iconfig -I../config -Ilib/eal/include -I../lib/eal/include -Ilib/eal/linux/include -I../lib/eal/linux/include -Ilib/eal/loongarch/include -I../lib/eal/loongarch/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/meter -I../lib/meter -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/pci -I../lib/pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/hash -I../lib/hash -Ilib/rcu -I../lib/rcu -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -std=c11 -O3 -include rte_config.h -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-strings !
-Wno-packed-not-aligned -Wno-missing-field-initializers -D_GNU_SOURCE -fPIC -march=loongarch64 -DALLOW_EXPERIMENTAL_API -DALLOW_INTERNAL_API -Wno-format-truncation -DBNXT_TF_APP_ID=0 -DSUPPORT_CFA_HW_P70=1 -DCFA_BLD_PRINT_OBJ=1 -DRTE_LOG_DEFAULT_LOGTYPE=pmd.net.bnxt -MD -MQ drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_vnic.c.o -MF drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_vnic.c.o.d -o drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_vnic.c.o -c ../drivers/net/bnxt/bnxt_vnic.c
./drivers/net/bnxt/bnxt_vnic.c: In function ‘bnxt_vnic_queue_db_init’:
./drivers/net/bnxt/bnxt_vnic.c:984:33: error: ‘RTE_HASH_BUCKET_ENTRIES’ undeclared (first use in this function); did you mean ‘RTE_HASH_ENTRIES_MAX’?
if (hash_tbl_params.entries <= RTE_HASH_BUCKET_ENTRIES)
^~~~~~~~~~~~~~~~~~~~~~~
RTE_HASH_ENTRIES_MAX
./drivers/net/bnxt/bnxt_vnic.c:984:33: note: each undeclared identifier is reported only once for each function it appears in
[829/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_irq.c.o
[830/2635] Linking static target drivers/libtmp_rte_net_axgbe.a
[831/2635] Generating rte_common_idpf.sym_chk with a custom command (wrapped by meson to capture output)
[832/2635] Generating rte_dma_skeleton.pmd.c with a custom command
[833/2635] Generating rte_net_atlantic.pmd.c with a custom command
[834/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_mpc.c.o
[835/2635] Generating rte_common_qat.pmd.c with a custom command
[836/2635] Generating rte_common_cnxk.pmd.c with a custom command
[837/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_txq.c.o
[838/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ring.c.o
[839/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_stats.c.o
[840/2635] Compiling C object drivers/libtmp_rte_dma_dpaa.a.p/dma_dpaa_dpaa_qdma.c.o
[841/2635] Generating rte_net_avp.pmd.c with a custom command
[842/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_rxq.c.o
[843/2635] Generating rte_dma_cnxk.sym_chk with a custom command (wrapped by meson to capture output)
[844/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_tf_ulp_bnxt_ulp.c.o
[845/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_reps.c.o
[846/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_txr.c.o
[847/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_flow.c.o
[848/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_rxr.c.o
[849/2635] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_bnx2x_stats.c.o
[850/2635] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_ecore_sp.c.o
[851/2635] Compiling C object lib/librte_pipeline.a.p/pipeline_rte_swx_pipeline.c.o
[852/2635] Generating rte_bus_dpaa.sym_chk with a custom command (wrapped by meson to capture output)
[853/2635] Generating rte_bus_fslmc.sym_chk with a custom command (wrapped by meson to capture output)
[854/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_ethdev.c.o
[855/2635] Generating eal.sym_chk with a custom command (wrapped by meson to capture output)
[856/2635] Generating ethdev.sym_chk with a custom command (wrapped by meson to capture output)
[857/2635] Compiling C object drivers/libtmp_rte_crypto_dpaa_sec.a.p/crypto_dpaa_sec_dpaa_sec.c.o
[858/2635] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_bnx2x.c.o
[859/2635] Compiling C object drivers/libtmp_rte_net_bnx2x.a.p/net_bnx2x_elink.c.o
[860/2635] Compiling C object drivers/libtmp_rte_net_bnxt.a.p/net_bnxt_bnxt_hwrm.c.o
[861/2635] Compiling C object lib/librte_vhost.a.p/vhost_virtio_net.c.o
ninja: build stopped: subcommand failed.
-------------------------------END LOGS------------------------------
next parent reply other threads:[~2024-11-18 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241118173613.94224-4-ajit.khaparde@broadcom.com>
2024-11-18 17:04 ` qemudev [this message]
2024-11-18 17:38 ` |WARNING| pw148587 " checkpatch
2024-11-18 18:20 ` |FAILURE| pw148585-148587 [PATCH] [3/3] " dpdklab
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=202411181704.4AIH4prA2350866@localhost.localdomain \
--to=qemudev@loongson.cn \
--cc=ajit.khaparde@broadcom.com \
--cc=test-report@dpdk.org \
--cc=zhoumin@loongson.cn \
/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).