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 1/3] add fips environment variable
Date: Wed, 9 Oct 2019 00:51:15 +0000 [thread overview]
Message-ID: <9DEEADBC57E43F4DA73B571777FECECA41DD876A@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1570512569-17999-1-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 1/3] add fips environment variable
>
> add fips_cryptodev environment variable
>
> Signed-off-by: yaobing <bingx.y.yao@intel.com>
> ---
> tests/cryptodev_common.py | 18 ++++++++++++++++++
> 1 file changed, 18 insertions(+)
>
> diff --git a/tests/cryptodev_common.py b/tests/cryptodev_common.py index
> 2e86bca..f521fbe 100644
> --- a/tests/cryptodev_common.py
> +++ b/tests/cryptodev_common.py
> @@ -44,12 +44,30 @@ def build_dpdk_with_cryptodev(test_case):
> if "kasumi_lib_path" in test_case.get_suite_cfg():
> kasumi_lib_path = test_case.get_suite_cfg()["kasumi_lib_path"]
>
> + fip_cflags_path = "'-I/opt/openssl-fips-2.0.16/include/'"
> + if "fip_cflags_path" in test_case.get_suite_cfg():
> + fip_cflags_path = test_case.get_suite_cfg()["fip_cflags_path"]
> +
> + fip_ldflags_path = "'-L/opt/openssl-fips-2.0.16/'"
> + if "fip_ldflags_path" in test_case.get_suite_cfg():
> + fip_cflags_path = test_case.get_suite_cfg()["fip_ldflags_path"]
> +
> + fip_library_path = "/opt/openssl-fips-2.0.16/"
> + if "fip_library_path" in test_case.get_suite_cfg():
> + fip_cflags_path = test_case.get_suite_cfg()["fip_library_path"]
> +
> test_case.dut.send_expect(
> "export LIBSSO_SNOW3G_PATH={}".format(snow3g_lib_path), "#")
> test_case.dut.send_expect(
> "export LIBSSO_ZUC_PATH={}".format(zuc_lib_path), "#")
> test_case.dut.send_expect(
> "export LIBSSO_KASUMI_PATH={}".format(kasumi_lib_path), "#")
> + test_case.dut.send_expect(
> + "export EXTRA_CFLAGS={}".format(fip_cflags_path), "#")
> + test_case.dut.send_expect(
> + "export EXTRA_LDFLAGS={}".format(fip_ldflags_path), "#")
> + test_case.dut.send_expect(
> + "export LD_LIBRARY_PATH={}".format(fip_library_path), "#")
>
> test_case.dut.send_expect(
> "sed -i
> 's/CONFIG_RTE_LIBRTE_PMD_AESNI_MB=n$/CONFIG_RTE_LIBRTE_PMD_AESNI_MB
> =y/' config/common_base", "# ")
> --
> 2.17.2
next prev parent 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 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
2019-10-10 5:36 ` Yao, BingX Y
2019-10-09 0:51 ` Chen, Zhaoyan [this message]
2019-10-10 5:36 ` [dts] [PATCH V1 1/3] add fips environment variable 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=9DEEADBC57E43F4DA73B571777FECECA41DD876A@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).