From: "Li, WenjieX A" <wenjiex.a.li@intel.com>
To: "Li, WenjieX A" <wenjiex.a.li@intel.com>,
"Zhao, XinfengX" <xinfengx.zhao@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhao, XinfengX" <xinfengx.zhao@intel.com>
Subject: Re: [dts] [PATCH V2] test_plan: add the test plan for cryptodev virtio unit test
Date: Fri, 10 May 2019 06:25:56 +0000 [thread overview]
Message-ID: <8688172CD5C0B74590FAE19D9579F94B536E31DD@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <8688172CD5C0B74590FAE19D9579F94B536E31BD@SHSMSX103.ccr.corp.intel.com>
System Message: WARNING/2 (<string>, line 33)
Title overline too short.
System Message: ERROR/3 (<string>, line 56)
Unexpected indentation.
System Message: WARNING/2 (<string>, line 57)
Block quote ends without a blank line; unexpected unindent.
System Message: ERROR/3 (<string>, line 72)
Unexpected indentation.
System Message: WARNING/2 (<string>, line 85)
Definition list ends without a blank line; unexpected unindent.
System Message: ERROR/3 (<string>, line 105)
Unexpected indentation.
Please ignore my last mail about VM-HOST topo.
BR,
Wenjie
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Li, WenjieX A
> Sent: Friday, May 10, 2019 2:16 PM
> To: Zhao, XinfengX <xinfengx.zhao@intel.com>; dts@dpdk.org
> Cc: Zhao, XinfengX <xinfengx.zhao@intel.com>
> Subject: Re: [dts] [PATCH V2] test_plan: add the test plan for cryptodev virtio
> unit test
>
> Hi Xinfeng,
>
> + +--------------+
> + | +--------+ |
> + | | VM | |
> + | +--------+ |
> + | |
> + | HOST |
> + +--------------+
>
> Maybe you can use below form to avoid errors when execute "make html".
>
> ::
>
> +--------------+
> | +--------+ |
> | | VM | |
> | +--------+ |
> | |
> | HOST |
> +--------------+
>
>
> BR,
> Wenjie
>
> > -----Original Message-----
> > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Xinfeng Zhao
> > Sent: Friday, May 10, 2019 5:16 AM
> > To: dts@dpdk.org
> > Cc: Zhao, XinfengX <xinfengx.zhao@intel.com>
> > Subject: [dts] [PATCH V2] test_plan: add the test plan for cryptodev
> > virtio unit test
> >
> > Signed-off-by: Xinfeng Zhao <xinfengx.zhao@intel.com>
> > ---
> > .../virtio_unit_cryptodev_func_test_plan.rst | 114
> +++++++++++++++++++++
> > 1 file changed, 114 insertions(+)
> > create mode 100644
> > test_plans/virtio_unit_cryptodev_func_test_plan.rst
> >
> > diff --git a/test_plans/virtio_unit_cryptodev_func_test_plan.rst
> > b/test_plans/virtio_unit_cryptodev_func_test_plan.rst
> > new file mode 100644
> > index 0000000..d603293
> > --- /dev/null
> > +++ b/test_plans/virtio_unit_cryptodev_func_test_plan.rst
> > @@ -0,0 +1,114 @@
> > +.. Copyright (c) 2018-2019 Intel Corporation
> > + All rights reserved.
> > +
> > + Redistribution and use in source and binary forms, with or without
> > + modification, are permitted provided that the following conditions
> > + are met:
> > +
> > + - Redistributions of source code must retain the above copyright
> > + notice, this list of conditions and the following disclaimer.
> > +
> > + - Redistributions in binary form must reproduce the above copyright
> > + notice, this list of conditions and the following disclaimer in
> > + the documentation and/or other materials provided with the
> > + distribution.
> > +
> > + - Neither the name of Intel Corporation nor the names of its
> > + contributors may be used to endorse or promote products derived
> > + from this software without specific prior written permission.
> > +
> > + THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
> > CONTRIBUTORS
> > + "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
> > + LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
> FITNESS
> > + FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
> > + COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
> > INDIRECT,
> > + INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> > + (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
> GOODS
> > OR
> > + SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
> > + HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
> > CONTRACT,
> > + STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> > + ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
> ADVISED
> > + OF THE POSSIBILITY OF SUCH DAMAGE.
> > +
> > +=====================
> > +CryptoDev virtio unit Tests
> > +=====================
> > +
> > +Description
> > +===========
> > +
> > +This document provides the plan for testing Cryptodev virtio API via
> > +Cryptodev
> > unit tests.
> > +Unit tests include supported Hardware and Software PMD(polling mode
> > +device)
> > and supported algorithms.
> > +
> > +This test suite will run all cryptodev virtio related unit test cases.
> > +Alternatively, you could execute the unit tests manually by app/test
> > +DPDK
> > application.
> > +
> > +Unit Test List
> > +==============
> > +
> > +- cryptodev_virtio_autotest
> > +
> > +Prerequisites
> > +=============
> > +
> > +qemu version >= 2.12
> > +in qemu enable vhost-user-crypto:
> > + ./configure --target-list=x86_64-softmmu --enable-vhost-crypto
> > +--prefix=/root/qemu-2.12 && make && make install the bin is in
> > +/root/qemu-2.12 folder, which is your specified
> > +
> > +Test Case Setup
> > +===============
> > + +--------------+
> > + | +--------+ |
> > + | | VM | |
> > + | +--------+ |
> > + | |
> > + | HOST |
> > + +--------------+
> > +
> > +In Host:
> > +# Build DPDK and vhost_crypto app
> > + enable CONFIG_RTE_LIBRTE_VHOST in config/common_base
> > + make install -j T=x86_64-native-linuxapp-gcc
> > + make -C examples/vhost_crypto
> > +
> > +# Run the dpdk vhost sample
> > + ./examples/vhost_crypto/build/vhost-crypto --file-
> prefix="vhost_crypto_1"
> > + [EAL options]
> > + [Cryptodev PMD]
> > + -- --cdev-queue-id 0
> > + --socket-file THE PATH OF SOCKET FILE
> > +
> > +# bind vfio-pci
> > + usertools/dpdk-devbind.py --bind=vfio-pci 0000:60:00.0
> > +0000:60:00.1
> > +
> > +# Start VM by the qemu
> > + taskset -c 11,12,13,14 /root/qemu-2.12/bin/qemu-system-x86_64
> > +-name
> > vm0
> > + -enable-kvm -pidfile /tmp/.vm0.pid
> > + -cpu host -smp 4
> > + -m 5120 -object memory-backend-file,id=mem,size=5120M,mem-
> > path=/mnt/huge,share=on -numa node,memdev=mem -mem-prealloc
> > + -net
> > + nic,vlan=0,macaddr=00:00:00:18:38:11,model=e1000,addr=1f -net
> > user,vlan=0,hostfwd=tcp:10.67.111.126:6000-:22
> > + -device virtio-serial
> > + -device
> virtserialport,chardev=vm0_qga0,name=org.qemu.guest_agent.0
> > + -daemonize -monitor unix:/tmp/vm0_monitor.sock,server,nowait
> > + -vnc :1
> > + -chardev socket,path=/tmp/vm0_crypto0.sock,id=vm0_crypto0
> > + -object
> > cryptodev-vhost-user,id=cryptodev0,chardev=vm0_crypto0 -device virtio-
> > crypto-pci,id=crypto0,cryptodev=cryptodev0
> > + -chardev socket,path=/tmp/vm0_crypto1.sock,id=vm0_crypto1
> > + -object
> > cryptodev-vhost-user,id=cryptodev1,chardev=vm0_crypto1 -device virtio-
> > crypto-pci,id=crypto1,cryptodev=cryptodev1
> > + -drive file=/root/VMs/virtio_crypto_test_710_1.img
> > + -device vfio-pci,host=0000:60:00.0,id=pt_0
> > + -device vfio-pci,host=0000:60:00.1,id=pt_1
> > +
> > +In VM
> > +# set virtio device
> > + modprobe uio_pci_generic
> > + echo -n 0000:00:04.0 > /sys/bus/pci/drivers/virtio-pci/unbind
> > + echo -n 0000:00:05.0 > /sys/bus/pci/drivers/virtio-pci/unbind
> > + echo "1af4 1054" > /sys/bus/pci/drivers/uio_pci_generic/new_id
> > +
> > +# Build the guest DPDK and app/test
> > +
> > +# Manually verify the app/test by this command, as example, in your
> > +build
> > folder:
> > + ./app/test -c 1 -n 1
> > + RTE>> cryptodev_virtio_autotest
> > +
> > +Expected all tests could pass in testing.
> > --
> > 2.7.4
prev parent reply other threads:[~2019-05-10 6:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 21:16 Xinfeng Zhao
2019-05-10 6:16 ` Li, WenjieX A
2019-05-10 6:25 ` Li, WenjieX A [this message]
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=8688172CD5C0B74590FAE19D9579F94B536E31DD@SHSMSX103.ccr.corp.intel.com \
--to=wenjiex.a.li@intel.com \
--cc=dts@dpdk.org \
--cc=xinfengx.zhao@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).