From: "Yao, Lei A" <lei.a.yao@intel.com>
To: "Mo, YufengX" <yufengx.mo@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V3 2/3] tests/malicious_driver_event_indication: update test plan
Date: Tue, 26 May 2020 02:08:14 +0000 [thread overview]
Message-ID: <c7142c3fda424d5e8a8b50ce2a7d6784@intel.com> (raw)
In-Reply-To: <20200525022315.3214-3-yufengx.mo@intel.com>
> -----Original Message-----
> From: Mo, YufengX <yufengx.mo@intel.com>
> Sent: Monday, May 25, 2020 10:23 AM
> To: dts@dpdk.org; Yao, Lei A <lei.a.yao@intel.com>
> Cc: Mo, YufengX <yufengx.mo@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
next prev parent reply other threads:[~2020-05-26 2:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 2:23 [dts] [PATCH V3 0/3] tests/malicious_driver_event_indication: upload test plan and automation script yufengmx
2020-05-25 2:23 ` [dts] [PATCH V3 1/3] tests/malicious_driver_event_indication: upload automation yufengmx
2020-05-25 2:23 ` [dts] [PATCH V3 2/3] tests/malicious_driver_event_indication: update test plan yufengmx
2020-05-26 2:08 ` Yao, Lei A [this message]
2020-05-25 2:23 ` [dts] [PATCH V3 3/3] tests/malicious_driver_event_indication: add " yufengmx
2020-05-26 2:16 ` Yao, Lei A
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=c7142c3fda424d5e8a8b50ce2a7d6784@intel.com \
--to=lei.a.yao@intel.com \
--cc=dts@dpdk.org \
--cc=yufengx.mo@intel.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).