automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: Edwin Brossette <edwin.brossette@6wind.com>,
	lijuan.tu@intel.com, daxuex.gao@intel.com,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	chenyux.huang@intel.com
Subject: [dpdk-test-report]|SUCCESS | dpdk-next-net-brcm|c0ada8f28a| Intel-Testing
Date: 22 Feb 2023 15:18:38 -0800	[thread overview]
Message-ID: <8251fc$kvvf86@orsmga001-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 4050 bytes --]


Test-Label: intel-Testing
Test-Status: SUCCESS 
_Testing PASS 

DPDK git repo: dpdk-next-net-brcm

commit c0ada8f28ae3385f76dea53e601ddf9d953f392a
Author: Edwin Brossette <edwin.brossette@6wind.com>
Date:   Mon Feb 6 18:11:13 2023 +0100

    bnxt: fix unwanted interrupt config on link state change
    
    When getting the device's info via bnxt_dev_info_get_op(), the device
    enables interrupts on link state changes because of the following line:
    
      > eth_dev->data->dev_conf.intr_conf.lsc = 1;
    
    Enabling this mode might not be wanted by the user.
    
    The flag RTE_ETH_DEV_INTR_LSC can be used to inform the above
    application that lsc interrupts are supported. Thus, checking this flag,
    the user can decide whether or not to enable these interrupts.
    
    Since there is no reason for a function meant to display config to
    actually modify it, remove this line. In addition, raise the dev_flag
    associated with this state on the device's initialization to show the
    device supports link state change interrupts.
    
    Fixes: 7bc8e9a227cc ("net/bnxt: support async link notification")
    Cc: stable@dpdk.org
    Signed-off-by: Edwin Brossette <edwin.brossette@6wind.com>
    Acked-by: Somnath Kotur <somnath.kotur@broadcom.com>
    Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

Testing Summary : 18 Case Done, 18 Successful, 0 Failures

Testbed #1: 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_jumbo_frames      | passed|
	  | vf_smoke    | test_vf_rss               | passed|
	  | vf_smoke    | test_vf_tx_rx_queue       | passed|
	  | virtio_smoke| test_virtio_loopback      | passed|
	  | virtio_smoke| test_virtio_pvp           | passed|
	  +-------------+---------------------------+-------+
	* Environment:
	  OS : Ubuntu 20.04.5 LTS       
	  Kernel : 5.8.0-63-generic         
	  GCC : 9.4.0-1ubuntu1~20.04.1        
	  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 20.04.5 LTS       
	  Kernel : 5.13.0-30-generic         
	  GCC : 9.4.0-1ubuntu1~20.04.1        
	  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-02-22 23:18 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='8251fc$kvvf86@orsmga001-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=chenyux.huang@intel.com \
    --cc=daxuex.gao@intel.com \
    --cc=edwin.brossette@6wind.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).