test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Tu, Lijuan" <lijuan.tu@intel.com>
To: "Jiang, YuX" <yux.jiang@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Jiang, YuX" <yux.jiang@intel.com>
Subject: Re: [dts] [PATCH V1 2/2] tests/unit_tests_cryptodev_func: support vdev param
Date: Wed, 9 Jun 2021 06:30:36 +0000	[thread overview]
Message-ID: <9e5b14e517794fb2b7d773836d134865@intel.com> (raw)
In-Reply-To: <20210528075312.23366-3-yux.jiang@intel.com>



> -----Original Message-----
> From: dts <dts-bounces@dpdk.org> On Behalf Of Yu Jiang
> Sent: 2021年5月28日 15:53
> To: dts@dpdk.org
> Cc: Jiang, YuX <yux.jiang@intel.com>
> Subject: [dts] [PATCH V1 2/2] tests/unit_tests_cryptodev_func: support vdev
> param
> 
> Based on dpdk commit 8bfdd8a7f0f1 ("test/crypto: refactor to use sub test
> suites"), unit test support vdev param.
> 
> Signed-off-by: Yu Jiang <yux.jiang@intel.com>
> ---
>  conf/unit_tests_cryptodev_func.cfg           | 32 +++++++++++++++++++++++++
>  tests/TestSuite_unit_tests_cryptodev_func.py | 36
> +++++++++++++++++++++++++++-
>  2 files changed, 67 insertions(+), 1 deletion(-)  create mode 100644
> conf/unit_tests_cryptodev_func.cfg
> 
> diff --git a/conf/unit_tests_cryptodev_func.cfg
> b/conf/unit_tests_cryptodev_func.cfg
> new file mode 100644
> index 0000000..0516293
> --- /dev/null
> +++ b/conf/unit_tests_cryptodev_func.cfg
> @@ -0,0 +1,32 @@
> +[suite]
> +
> +# vdev which is supported from 21.05rc3 commit id: 8bfdd8a7f0
> +test/crypto: refactor to use sub test suites
> +[test_cryptodev_aesni_gcm_autotest]
> +devtype="crypto_aesni_gcm"
> +
> +[test_cryptodev_aesni_mb_autotest]
> +devtype="crypto_aesni_mb"
> +
> +[test_cryptodev_null_autotest]
> +devtype="crypto_null"
> +
> +[test_cryptodev_openssl_autotest]
> +devtype="crypto_openssl"
> +
> +[test_cryptodev_qat_asym_autotest]
> +devtype="crypto_qat"
> +
> +[test_cryptodev_qat_autotest]
> +devtype="crypto_qat"
> +
> +[test_cryptodev_scheduler_autotest]
> +devtype="crypto_scheduler"
> +
> +[test_cryptodev_sw_kasumi_autotest]
> +devtype="crypto_kasumi"
> +
> +[test_cryptodev_sw_snow3g_autotest]
> +devtype="crypto_snow3g"
> +
> +[test_cryptodev_sw_zuc_autotest]
> +devtype="crypto_zuc"
> diff --git a/tests/TestSuite_unit_tests_cryptodev_func.py
> b/tests/TestSuite_unit_tests_cryptodev_func.py
> index 98425d4..1564c7f 100644
> --- a/tests/TestSuite_unit_tests_cryptodev_func.py
> +++ b/tests/TestSuite_unit_tests_cryptodev_func.py
> @@ -53,6 +53,39 @@ class UnitTestsCryptodev(TestCase):
>      def tear_down_all(self):
>          cc.clear_dpdk_config(self)
> 
> +    def _get_crypto_device(self, num):
> +        device = {}
> +        if self.get_case_cfg()["devtype"] == "crypto_aesni_mb":
> +            dev = "crypto_aesni_mb"
> +        elif self.get_case_cfg()["devtype"] == "crypto_qat":
> +            w = cc.get_qat_devices(self, cpm_num=1, num=num)
> +#            device["a"] = ' -a '.join(w)

Please remove some useless comments, thanks

> +            device["vdev"] = None
> +        elif self.get_case_cfg()["devtype"] == "crypto_openssl":
> +            dev = "crypto_openssl"
> +        elif self.get_case_cfg()["devtype"] == "crypto_aesni_gcm":
> +            dev = "crypto_aesni_gcm"
> +        elif self.get_case_cfg()["devtype"] == "crypto_kasumi":
> +            dev = "crypto_kasumi"
> +        elif self.get_case_cfg()["devtype"] == "crypto_snow3g":
> +            dev = "crypto_snow3g"
> +        elif self.get_case_cfg()["devtype"] == "crypto_zuc":
> +            dev = "crypto_zuc"
> +        elif self.get_case_cfg()["devtype"] == "crypto_null":
> +            dev = "crypto_null"
> +        else:
> +            return {}
> +
> +        if not device:
> +            vdev_list = []
> +            for i in range(num):
> +                vdev = "{}{}".format(dev, i)
> +                vdev_list.append(vdev)
> +        #    device["a"] = "0000:00:00.0"
> +            device["vdev"] = ' --vdev '.join(vdev_list)
> +
> +        return device
> +
>      def test_cryptodev_qat_autotest(self):
>          self.__run_unit_test("cryptodev_qat_autotest")
> 
> @@ -105,7 +138,8 @@ class UnitTestsCryptodev(TestCase):
>          self.__run_unit_test("cryptodev_scheduler_autotest")
> 
>      def __run_unit_test(self, testsuite, timeout=600):
> -        eal_opt_str = cc.get_eal_opt_str(self)
> +        devices = self._get_crypto_device(num=1)
> +        eal_opt_str = cc.get_eal_opt_str(self, devices)
>          w = cc.get_qat_devices(self, num=1)
> 
>          self.logger.info("STEP_TEST: " + testsuite)
> --
> 2.7.4


  reply	other threads:[~2021-06-09  6:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28  7:53 [dts] [PATCH V1 0/2] cryptodev unit test " Yu Jiang
2021-05-28  7:53 ` [dts] [PATCH V1 1/2] tests/virtio_unit_cryptodev_func: " Yu Jiang
2021-05-28  7:53 ` [dts] [PATCH V1 2/2] tests/unit_tests_cryptodev_func: " Yu Jiang
2021-06-09  6:30   ` Tu, Lijuan [this message]
2021-06-02  2:49 ` [dts] [PATCH V1 0/2] cryptodev unit test " Jiang, YuX
  -- strict thread matches above, loose matches on Subject: below --
2021-05-28  3:48 [dts] [PATCH V1 2/2] tests/unit_tests_cryptodev_func: " Yu Jiang

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=9e5b14e517794fb2b7d773836d134865@intel.com \
    --to=lijuan.tu@intel.com \
    --cc=dts@dpdk.org \
    --cc=yux.jiang@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).