From: yaobing <bingx.y.yao@intel.com>
To: dts@dpdk.org
Cc: yaobing <bingx.y.yao@intel.com>
Subject: [dts] [PATCH V1 1/3] add fips environment variable
Date: Tue, 8 Oct 2019 13:29:27 +0800 [thread overview]
Message-ID: <1570512569-17999-1-git-send-email-bingx.y.yao@intel.com> (raw)
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 reply other threads:[~2019-10-08 5:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-08 5:29 yaobing [this message]
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 ` [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=1570512569-17999-1-git-send-email-bingx.y.yao@intel.com \
--to=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).