From: Ciara Power <ciara.power@intel.com>
To: stable@dpdk.org
Cc: luca.boccassi@gmail.com, brian.dooley@intel.com,
Ciara Power <ciara.power@intel.com>
Subject: [PATCH 20.11.10] test/crypto: skip some synchronous tests with CPU crypto
Date: Thu, 19 Oct 2023 12:48:32 +0000 [thread overview]
Message-ID: <20231019124832.1242938-1-ciara.power@intel.com> (raw)
[ upstream commit 38318ce05459391344acb53a73c9a99537a0bd0f ]
Some synchronous tests are not supported for CPU crypto and
need to be skipped. This commit adds in extra skips for these tests.
Fixes: 55ab4a8 ("test/crypto: disable wireless cases for CPU crypto API")
Signed-off-by: Brian Dooley <brian.dooley@intel.com>
Signed-off-by: Ciara Power <ciara.power@intel.com>
---
app/test/test_cryptodev.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
index 2e76763e09..60fe8a1fbf 100644
--- a/app/test/test_cryptodev.c
+++ b/app/test/test_cryptodev.c
@@ -5800,6 +5800,9 @@ test_zuc_auth_cipher(const struct wireless_test_data *tdata,
&cap_idx) == NULL)
return -ENOTSUP;
+ if (gbl_action_type == RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO)
+ return -ENOTSUP;
+
rte_cryptodev_info_get(ts_params->valid_devs[0], &dev_info);
uint64_t feat_flags = dev_info.feature_flags;
@@ -6828,6 +6831,8 @@ test_mixed_auth_cipher(const struct mixed_cipher_auth_test_data *tdata,
return -ENOTSUP;
if (global_api_test_type == CRYPTODEV_RAW_API_TEST)
return -ENOTSUP;
+ if (gbl_action_type == RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO)
+ return -ENOTSUP;
rte_cryptodev_info_get(ts_params->valid_devs[0], &dev_info);
--
2.25.1
next reply other threads:[~2023-10-19 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-19 12:48 Ciara Power [this message]
2023-10-23 15:50 ` Luca Boccassi
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=20231019124832.1242938-1-ciara.power@intel.com \
--to=ciara.power@intel.com \
--cc=brian.dooley@intel.com \
--cc=luca.boccassi@gmail.com \
--cc=stable@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).