test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Chen, Zhaoyan" <zhaoyan.chen@intel.com>
To: "Yao, BingX Y" <bingx.y.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Cc: "Yao, BingX Y" <bingx.y.yao@intel.com>,
	"Chen, Zhaoyan" <zhaoyan.chen@intel.com>
Subject: Re: [dts] [PATCH V1 3/3] add fips_cryptodev config
Date: Wed, 9 Oct 2019 00:50:58 +0000	[thread overview]
Message-ID: <9DEEADBC57E43F4DA73B571777FECECA41DD8721@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1570512569-17999-3-git-send-email-bingx.y.yao@intel.com>

Acked-by: Chen, Zhaoyan <zhaoyan.chen@intel.com>



Regards,
Zhaoyan Chen

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of yaobing
> Sent: Tuesday, October 8, 2019 1:29 PM
> To: dts@dpdk.org
> Cc: Yao, BingX Y <bingx.y.yao@intel.com>
> Subject: [dts] [PATCH V1 3/3] add fips_cryptodev config
> 
> add fips_cryptodev config
> 
> Signed-off-by: yaobing <bingx.y.yao@intel.com>
> ---
>  conf/fips_cryptodev.cfg | 102 ++++++++++++++++++++++++++++++++++++++++
>  1 file changed, 102 insertions(+)
>  create mode 100644 conf/fips_cryptodev.cfg
> 
> diff --git a/conf/fips_cryptodev.cfg b/conf/fips_cryptodev.cfg new file mode 100644
> index 0000000..b3fd6b5
> --- /dev/null
> +++ b/conf/fips_cryptodev.cfg
> @@ -0,0 +1,102 @@
> +[suite]
> +# Cryptodev common options qat device idcrypto_dev_id="37c9"
> +crypto_dev_id="37c9"
> +
> +l="9,10,66"
> +socket-mem="2048,2048 --legacy-mem"
> +n=6
> +
> +vdev="crypto_aesni_mb_pmd_1"
> +
> +[test_fips_aesni_gcm_gcm]
> +w="0000:af:00.0"
> +req-file="/root/FIPS/GCM/req"
> +rsp-file="/root/FIPS/GCM/resp"
> +cryptodev="crypto_aesni_gcm_pmd_1"
> +
> +[test_fips_aesni_mb_3des]
> +w="0000:af:00.0"
> +req-file="/root/FIPS/TDES/req"
> +rsp-file="/root/FIPS/TDES/resp"
> +cryptodev="crypto_aesni_mb_pmd_1"
> +
> +[test_fips_aesni_mb_aes]
> +w="0000:af:00.0"
> +req-file="/root/FIPS/AES/req"
> +rsp-file="/root/FIPS/AES/resp"
> +cryptodev="crypto_aesni_mb_pmd_1"
> +
> +[test_fips_aesni_mb_ccm]
> +w="0000:af:00.0"
> +req-file="/root/FIPS/CCM/req"
> +rsp-file="/root/FIPS/CCM/resp"
> +
> +[test_fips_aesni_mb_cmac]
> +w="0000:af:00.0"
> +req-file="/root/FIPS/CMAC/req"
> +rsp-file="/root/FIPS/CMAC/resp"
> +
> +[test_fips_aesni_mb_hmac]
> +w="0000:af:00.0"
> +req-file="/root/FIPS/HMAC/req"
> +rsp-file="/root/FIPS/HMAC/resp"
> +
> +[test_fips_broken_test]
> +w="0000:1a:01.0"
> +req-file="/root/FIPS/AES/req"
> +rsp-file="/root/FIPS/AES/resp"
> +
> +[test_fips_openssl_3des]
> +req-file="/root/FIPS/TDES/req"
> +rsp-file="/root/FIPS/TDES/resp"
> +
> +[test_fips_openssl_aes]
> +req-file="/root/FIPS/AES/req"
> +rsp-file="/root/FIPS/AES/resp"
> +
> +[test_fips_openssl_ccm]
> +req-file="/root/FIPS/CCM/req"
> +rsp-file="/root/FIPS/CCM/resp"
> +
> +[test_fips_openssl_gcm]
> +req-file="/root/FIPS/GCM/req"
> +rsp-file="/root/FIPS/GCM/resp"
> +
> +[test_fips_openssl_hmac]
> +req-file="/root/FIPS/HMAC/req"
> +rsp-file="/root/FIPS/HMAC/resp"
> +
> +[test_fips_qat_3des]
> +w="0000:1a:01.0"
> +req-file="/root/FIPS/TDES/req"
> +rsp-file="/root/FIPS/TDES/resp"
> +
> +[test_fips_qat_aes]
> +w="0000:1a:01.0"
> +req-file="/root/FIPS/AES/req"
> +rsp-file="/root/FIPS/AES/resp"
> +
> +[test_fips_qat_ccm]
> +w="0000:1a:01.0"
> +req-file="/root/FIPS/CCM/req"
> +rsp-file="/root/FIPS/CCM/resp"
> +
> +[test_fips_qat_cmac]
> +w="0000:1a:01.0"
> +req-file="/root/FIPS/CMAC/req"
> +rsp-file="/root/FIPS/CMAC/resp"
> +
> +[test_fips_qat_gcm]
> +w="0000:1a:01.0"
> +req-file="/root/FIPS/GCM/req"
> +rsp-file="/root/FIPS/GCM/resp"
> +
> +[test_fips_qat_hmac]
> +w="0000:1a:01.0"
> +req-file="/root/FIPS/HMAC/req"
> +rsp-file="/root/FIPS/HMAC/resp"
> +
> +[test_fips_self_test]
> +w="0000:1a:01.0"
> +req-file="/root/FIPS/AES/req"
> +rsp-file="/root/FIPS/AES/resp"
> --
> 2.17.2


  reply	other threads:[~2019-10-09  0:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-08  5:29 [dts] [PATCH V1 1/3] add fips environment variable yaobing
2019-10-08  5:29 ` [dts] [PATCH V1 2/3] add case suite fips_cryptodev yaobing
2019-10-09  0:51   ` Chen, Zhaoyan
2019-10-10  5:36   ` Yao, BingX Y
2019-10-08  5:29 ` [dts] [PATCH V1 3/3] add fips_cryptodev config yaobing
2019-10-09  0:50   ` Chen, Zhaoyan [this message]
2019-10-10  5:36   ` Yao, BingX Y
2019-10-09  0:51 ` [dts] [PATCH V1 1/3] add fips environment variable Chen, Zhaoyan
2019-10-10  5:36 ` Yao, BingX Y
2019-10-12  5:42 ` Tu, Lijuan

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=9DEEADBC57E43F4DA73B571777FECECA41DD8721@SHSMSX104.ccr.corp.intel.com \
    --to=zhaoyan.chen@intel.com \
    --cc=bingx.y.yao@intel.com \
    --cc=dts@dpdk.org \
    /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).