[dts] [PATCH V3 2/3] tests/malicious_driver_event_indication: update test plan

[Yao, Lei A]

> -----Original Message-----
> From: Mo, YufengX <yufengx.mo at intel.com>
> Sent: Monday, May 25, 2020 10:23 AM
> To: dts at dpdk.org; Yao, Lei A <lei.a.yao at intel.com>
> Cc: Mo, YufengX <yufengx.mo at intel.com>
> Subject: [dts][PATCH V3 2/3] tests/malicious_driver_event_indication:
> update test plan
> 
> 


> +2. Launch PF by testpmd
> +    ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x03 -n 4 --file-prefix=test1
> -w [pic of PF] -- -i
Should be pci
> +
> +3. Launch VF by testpmd
> +    ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x03 -n 4 --file-prefix=lei1 -
> w [pic of VF] -- -i
Should be pci
> +    > set fwd txonly
> +    > start
> +
> +4. Check the PF can detect the VF's unexpected behavior and output
> warning log
> +    testpmd>
> +    i40e_dev_alarm_handler(): ICR0: malicious programming detected
> +    i40e_handle_mdd_event(): Malicious Driver Detection event 0x00 on TX
> queue 65 PF number 0x01 VF number 0x40 device 0000:18:00.1
> +    i40e_handle_mdd_event(): TX driver issue detected on PF
> +    i40e_handle_mdd_event(): TX driver issue detected on VF 0 1times
> +
> +
> +Test Case2:  Check the event counter number for malicious driver events
> +=========================================================
> ==============
> +1. Generate i40e VF when PF is binded to igb_uio driver
> +    echo 1 > /sys/bus/pci/devices/0000\:18\:00.1/max_vfs
> +
> +2. Launch PF by testpmd
> +    ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x03 -n 4 --file-prefix=test1
> -w [pic of PF] -- -i
Should be pci
> +
> +3. launch VF by testpmd and start txonly mode 3 times:
> +    repeat following step 3 times
> +    ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x03 -n 4 --file-prefix=lei1 -
> w [pic of VF] -- -i
Should be pci
> +    > set fwd txonly
> +    > start