From: Rami Rosen <ramirose@gmail.com>
To: yong.liu@intel.com
Cc: dts@dpdk.org, qian.q.xu@intel.com, Rami Rosen <ramirose@gmail.com>
Subject: [dts] [PATCH] test_plans: remove deprcecated CONFIG_RTE_LIBRTE_VIRTIO_DEBUG_INIT
Date: Sat, 1 Sep 2018 15:00:50 +0300 [thread overview]
Message-ID: <20180901120050.14200-1-ramirose@gmail.com> (raw)
This patch removes two occurences of CONFIG_RTE_LIBRTE_VIRTIO_DEBUG_INIT
in virtio_1.0 test plan, as CONFIG_RTE_LIBRTE_VIRTIO_DEBUG_INIT
is deprecated. The following DPDK commit, which was
applied already in DPDK 18.02, removed it from config/common_base:
0062818856c3 ("net/virtio: implement dynamic logging").
Signed-off-by: Rami Rosen <ramirose@gmail.com>
---
test_plans/virtio_1.0_test_plan.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/test_plans/virtio_1.0_test_plan.rst b/test_plans/virtio_1.0_test_plan.rst
index 265c586..53080af 100644
--- a/test_plans/virtio_1.0_test_plan.rst
+++ b/test_plans/virtio_1.0_test_plan.rst
@@ -62,7 +62,7 @@ Note: For virtio1.0 usage, we need use qemu version >2.4, such as 2.4.1 or 2.5.0
-netdev tap,id=ipvm1,ifname=tap3,script=/etc/qemu-ifup -device rtl8139,netdev=ipvm1,id=net0,mac=00:00:00:00:10:01 -nographic
-3. In the VM, change the config file--common_linuxapp, "CONFIG_RTE_LIBRTE_VIRTIO_DEBUG_INIT=y"; Run dpdk testpmd in VM::
+3. In the VM, run dpdk testpmd:
./<dpdk_folder>/tools/dpdk_nic_bind.py --bind igb_uio 00:03.0
@@ -122,7 +122,7 @@ Note: For virtio1.0 usage, we need use qemu version >2.4, such as 2.4.1 or 2.5.0
-netdev tap,id=ipvm1,ifname=tap3,script=/etc/qemu-ifup -device rtl8139,netdev=ipvm1,id=net0,mac=00:00:00:00:10:01 -nographic
-3. In the VM, change the config file--common_linuxapp, "CONFIG_RTE_LIBRTE_VIRTIO_DEBUG_INIT=y"; Run dpdk testpmd in VM::
+3. In the VM, run dpdk testpmd:
./<dpdk_folder>/tools/dpdk_nic_bind.py --bind igb_uio 00:03.0
--
2.17.1
next reply other threads:[~2018-09-01 12:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 12:00 Rami Rosen [this message]
2018-09-27 17:31 ` Lijuan Tu
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=20180901120050.14200-1-ramirose@gmail.com \
--to=ramirose@gmail.com \
--cc=dts@dpdk.org \
--cc=qian.q.xu@intel.com \
--cc=yong.liu@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).