From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id CF71CA0540; Wed, 6 Jul 2022 04:38:18 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C16D740FAE; Wed, 6 Jul 2022 04:38:18 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by mails.dpdk.org (Postfix) with ESMTP id 525A740395 for ; Wed, 6 Jul 2022 04:38:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1657075097; x=1688611097; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=otLcfzEI1Lkpujh53hulJWP9OTWyJg0kRksIyXFHzSg=; b=h+ujvNsY7aS+9tx68GaXjpZuP/1ff+QX+Og4SsxWbg3xOoBmT/aerlKB KWmf86Cyy/26rYShDQVV+Og/O5QdcHhXTOLctgHD0ytYQspC6g9oVileO eIwJ79WrzWHLj4kPqg4x7a2HsEswzstg+WskNWe4ISPOCcIXSBq7JtXKb BDeVhgWOqCq+eWt6Eclh/fCph75/ASpDYq3GS1V86RXAePtgDtzB7oJGa HynsZbGzV1MXr1kkkvx/yyhHvK5XF4Qrv0/hF40VF+y1sMaOBTeCKVWh0 Ef4gySHlk0XEfejkTEFizQ6XRdZE0W8zuD00Jb8GKZ2SrjAPOpA25xi9e A==; X-IronPort-AV: E=McAfee;i="6400,9594,10399"; a="369941349" X-IronPort-AV: E=Sophos;i="5.92,248,1650956400"; d="scan'208";a="369941349" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jul 2022 19:38:16 -0700 X-IronPort-AV: E=Sophos;i="5.92,248,1650956400"; d="scan'208";a="625684839" Received: from unknown (HELO localhost.localdomain) ([10.239.252.248]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 05 Jul 2022 19:38:15 -0700 From: Weiyuan Li To: dts@dpdk.org, yuan.peng@intel.com Cc: Weiyuan Li Subject: [dts][PATCH V2 3/4] test_plans/kernelpf_iavf: update dts code for driver change Date: Wed, 6 Jul 2022 10:38:05 +0800 Message-Id: <20220706023806.27825-3-weiyuanx.li@intel.com> X-Mailer: git-send-email 2.27.0 In-Reply-To: <20220706023806.27825-1-weiyuanx.li@intel.com> References: <20220706023806.27825-1-weiyuanx.li@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 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 The out-tree driver has vf-vlan-pruning option,but in-tree driver has not. So we need different action to enable vlan filter when we validate the vlan filter function with in-tree and out-tree kernel drvier. Signed-off-by: Weiyuan Li --- v2: -fix format issue test_plans/kernelpf_iavf_test_plan.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/test_plans/kernelpf_iavf_test_plan.rst b/test_plans/kernelpf_iavf_test_plan.rst index 8c7d1ad5..f044e3cc 100644 --- a/test_plans/kernelpf_iavf_test_plan.rst +++ b/test_plans/kernelpf_iavf_test_plan.rst @@ -28,6 +28,9 @@ Get the pci device id of DUT, for example:: 0000:18:00.0 'Device 1592' if=enp24s0f0 drv=ice unused=igb_uio 0000:18:00.1 'Device 1592' if=enp24s0f1 drv=ice unused=igb_uio +If the driver is out tree enable pf vf-vlan-pruning flags:: + ethtool --set-priv-flags $PF_INTF vf-vlan-pruning on + Create 1 VF from 1 kernel PF:: echo 1 > /sys/bus/pci/devices/0000\:18\:00.0/sriov_numvfs -- 2.27.0