From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0679AA04C7; Tue, 15 Sep 2020 13:41:28 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 00F381C10C; Tue, 15 Sep 2020 13:41:28 +0200 (CEST) Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 1ADA41BE8E for ; Tue, 15 Sep 2020 13:41:25 +0200 (CEST) IronPort-SDR: tKj2rP1gfNkJHaRXf76oUy50ILMSgLztoea1C/EVYDXsV80TPohYE4xiqTmHgUeH54muNc+njc HeTZW1h/W6tQ== X-IronPort-AV: E=McAfee;i="6000,8403,9744"; a="223423717" X-IronPort-AV: E=Sophos;i="5.76,429,1592895600"; d="scan'208";a="223423717" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Sep 2020 04:41:25 -0700 IronPort-SDR: PKew6GPG5BIK5rEcUh64VVWtK010/54rq/CWIw/SLr8Olbaxrv8+JOyB4akSTvv8zOl6qyw8yT 6bJY5QobI+KQ== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.76,429,1592895600"; d="scan'208";a="379710618" Received: from unknown (HELO dpdk-zhaohy-t.localdomain) ([10.240.183.68]) by orsmga001.jf.intel.com with ESMTP; 15 Sep 2020 04:41:24 -0700 From: Haiyang Zhao To: dts@dpdk.org Cc: Haiyang Zhao Date: Tue, 15 Sep 2020 19:24:44 +0800 Message-Id: <1600169086-340540-16-git-send-email-haiyangx.zhao@intel.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <1600169086-340540-1-git-send-email-haiyangx.zhao@intel.com> References: <1600169086-340540-1-git-send-email-haiyangx.zhao@intel.com> Subject: [dts] [PATCH V1 15/17] test_plans/virtio_event_idx_interrupt: fix build warnings and errors X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" *.fix build warnings and errors Signed-off-by: Haiyang Zhao --- .../virtio_event_idx_interrupt_test_plan.rst | 48 +++++++++++----------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/test_plans/virtio_event_idx_interrupt_test_plan.rst b/test_plans/virtio_event_idx_interrupt_test_plan.rst index 6cb00ab..df05529 100644 --- a/test_plans/virtio_event_idx_interrupt_test_plan.rst +++ b/test_plans/virtio_event_idx_interrupt_test_plan.rst @@ -292,8 +292,8 @@ Test Case 7: wake up vhost-user core with event idx interrupt mode and cbdma ena 3. On VM, set ip for virtio device and send packets to vhost:: - ifconfig [ens3] 1.1.1.2 # [ens3] is the name of virtio-net - ping 1.1.1.3 + ifconfig [ens3] 1.1.1.2 # [ens3] is the name of virtio-net + ping 1.1.1.3 4. Check vhost related core is waked up by reading l3fwd-power log. @@ -326,31 +326,31 @@ Test Case 8: wake up vhost-user cores with event idx interrupt mode and cbdma en 3. Set vitio-net with 16 quques and give vitio-net ip address:: - ethtool -L ens4 combined 16 # [ens3] is the name of virtio-net - ifconfig ens4 1.1.1.1 + ethtool -L ens4 combined 16 # [ens3] is the name of virtio-net + ifconfig ens4 1.1.1.1 4. Send packets with different IPs from virtio-net, notice to bind each vcpu to different send packets process:: - taskset -c 0 ping 1.1.1.2 - taskset -c 1 ping 1.1.1.3 - taskset -c 2 ping 1.1.1.4 - taskset -c 3 ping 1.1.1.5 - taskset -c 4 ping 1.1.1.6 - taskset -c 5 ping 1.1.1.7 - taskset -c 6 ping 1.1.1.8 - taskset -c 7 ping 1.1.1.9 - taskset -c 8 ping 1.1.1.2 - taskset -c 9 ping 1.1.1.2 - taskset -c 10 ping 1.1.1.2 - taskset -c 11 ping 1.1.1.2 - taskset -c 12 ping 1.1.1.2 - taskset -c 13 ping 1.1.1.2 - taskset -c 14 ping 1.1.1.2 - taskset -c 15 ping 1.1.1.2 + taskset -c 0 ping 1.1.1.2 + taskset -c 1 ping 1.1.1.3 + taskset -c 2 ping 1.1.1.4 + taskset -c 3 ping 1.1.1.5 + taskset -c 4 ping 1.1.1.6 + taskset -c 5 ping 1.1.1.7 + taskset -c 6 ping 1.1.1.8 + taskset -c 7 ping 1.1.1.9 + taskset -c 8 ping 1.1.1.2 + taskset -c 9 ping 1.1.1.2 + taskset -c 10 ping 1.1.1.2 + taskset -c 11 ping 1.1.1.2 + taskset -c 12 ping 1.1.1.2 + taskset -c 13 ping 1.1.1.2 + taskset -c 14 ping 1.1.1.2 + taskset -c 15 ping 1.1.1.2 5. Check vhost related cores are waked up with l3fwd-power log, such as following:: - L3FWD_POWER: lcore 0 is waked up from rx interrupt on port 0 queue 0 - ..... - ..... - L3FWD_POWER: lcore 15 is waked up from rx interrupt on port 0 queue 15 + L3FWD_POWER: lcore 0 is waked up from rx interrupt on port 0 queue 0 + ..... + ..... + L3FWD_POWER: lcore 15 is waked up from rx interrupt on port 0 queue 15 -- 1.8.3.1