From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: Jerin Jacob <jerinj@marvell.com>,
chenyux.huang@intel.com, Harman Kalra <hkalra@marvell.com>,
lijuan.tu@intel.com, daxuex.gao@intel.com
Subject: [dpdk-test-report]|SUCCESS | dpdk-next-net-mrvl|9acb447c72| Intel-Testing
Date: 12 Jun 2023 23:41:28 -0700 [thread overview]
Message-ID: <d52771$m630lr@orsmga001-auth.jf.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3820 bytes --]
Test-Label: intel-Testing
Test-Status: SUCCESS
_Testing PASS
DPDK git repo: dpdk-next-net-mrvl
commit 9acb447c72a27228b520ff833cafa5aa8f43a431
Author: Harman Kalra <hkalra@marvell.com>
Date: Mon Jun 5 14:14:23 2023 +0530
common/cnxk: fix mailbox timeout due to deadlock
PF receives all the VFs mailbox/FLR messages which it forwards to AF.
This is all handled by interrupt thread. Due to mailbox locking in place
a deadlock situation may arise which may lead to mailbox timeout.
Say at T1 - PF sends its own mailbox to AF and wait for response
(PF is holding mailbox lock)
T2 - VF mailbox/FLR interrupt comes and interrupt thread process it.
Mailbox handling requires mailbox lock to send messages to AF, but lock
is hold by PF. Interrupt thread spins at this point only and misses
to ack the AFs response of PF messages which was sent at T1. Hence
message sent at T1 gets timed out.
As a solution to this scenario, creating a dedicated thread which
does the VFs mailbox and FLR processing. When no message this thread
waits on conditional variable and get waken up by interrupt thread
on any mailbox/FLR interrupt reception.
Fixes: 585bb3e538f9 ("common/cnxk: add VF support to base device class")
Cc: stable@dpdk.org
Signed-off-by: Harman Kalra <hkalra@marvell.com>
Testing Summary : 15 Case Done, 15 Successful, 0 Failures
Testbed #1: 6 Case Done, 6 Successful, 0 Failures
* Test result details:
+---------+---------------------+-------+
| suite | case | status|
+---------+---------------------+-------+
| pf_smoke| test_pf_jumbo_frames| passed|
| pf_smoke| test_pf_rss | passed|
| pf_smoke| test_pf_tx_rx_queue | passed|
| vf_smoke| test_vf_jumbo_frames| passed|
| vf_smoke| test_vf_rss | passed|
| vf_smoke| test_vf_tx_rx_queue | passed|
+---------+---------------------+-------+
* Environment:
OS : Ubuntu 22.04.2 LTS
Kernel : 5.15.0-60-generic
GCC : 11.3.0-1ubuntu1~22.04
NIC : Ethernet Controller E810-C for SFP
Target : x86_64-native-linuxapp-gcc
Testbed #2: 9 Case Done, 9 Successful, 0 Failures
* Test result details:
+-------------+---------------------------+-------+
| suite | case | status|
+-------------+---------------------------+-------+
| asan_smoke | test_rxtx_with_ASan_enable| passed|
| pf_smoke | test_pf_jumbo_frames | passed|
| pf_smoke | test_pf_rss | passed|
| pf_smoke | test_pf_tx_rx_queue | passed|
| vf_smoke | test_vf_rss | passed|
| vf_smoke | test_vf_tx_rx_queue | passed|
| vf_smoke | test_vf_jumbo_frames | n/a |
| virtio_smoke| test_virtio_loopback | passed|
| virtio_smoke| test_virtio_pvp | passed|
+-------------+---------------------------+-------+
* Environment:
OS : Ubuntu 22.04.2 LTS
Kernel : 5.15.0-60-generic
GCC : 11.3.0-1ubuntu1~22.04
NIC : Ethernet Controller XL710 for 40GbE QSFP+
Target : x86_64-native-linuxapp-gcc
TestPlan:
pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test_plan.rst
vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test_plan.rst
asan_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/asan_smoke_test_plan.rst
TestSuite:
pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py
asan_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_asan_smoke.py
DPDK STV team
reply other threads:[~2023-06-13 6:41 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='d52771$m630lr@orsmga001-auth.jf.intel.com' \
--to=sys_stv@intel.com \
--cc=chenyux.huang@intel.com \
--cc=daxuex.gao@intel.com \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=lijuan.tu@intel.com \
--cc=test-report@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;
as well as URLs for NNTP newsgroup(s).