From: Kevin Traynor <ktraynor@redhat.com>
To: Kai Ji <kai.ji@intel.com>, stable@dpdk.org
Cc: hemant.agrawal@nxp.com
Subject: Re: [PATCH 21.11.1 v1] test/crypto: skip oop test for raw api
Date: Mon, 25 Apr 2022 15:28:20 +0100 [thread overview]
Message-ID: <faeeb57f-fa5f-0d1e-7e68-6c7030b42c82@redhat.com> (raw)
In-Reply-To: <20220414172353.19105-1-kai.ji@intel.com>
On 14/04/2022 18:23, Kai Ji wrote:
> Add in api test type check to skip unsupported aead OOP testcase
> in raw API test.
>
> Fixes: cd8166c28cd1 ("test/crypto: add raw API test for dpaax")
> Cc: hemant.agrawal@nxp.com
>
> Signed-off-by: Kai Ji <kai.ji@intel.com>
> Tested-by: Poczatek, Jakub <jakub.poczatek@intel.com>
> ---
> app/test/test_cryptodev.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
> index 16431efc88..4eedc8e198 100644
> --- a/app/test/test_cryptodev.c
> +++ b/app/test/test_cryptodev.c
> @@ -10547,9 +10547,16 @@ test_authenticated_encryption_oop(const struct aead_test_data *tdata)
> rte_cryptodev_info_get(ts_params->valid_devs[0], &dev_info);
> uint64_t feat_flags = dev_info.feature_flags;
>
> + /* not supported with CPU crypto and raw data-path APIs*/
> + if (gbl_action_type == RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO ||
> + global_api_test_type == CRYPTODEV_RAW_API_TEST)
> + return TEST_SKIPPED;
> +
> if ((global_api_test_type == CRYPTODEV_RAW_API_TEST) &&
> - (!(feat_flags & RTE_CRYPTODEV_FF_SYM_RAW_DP)))
> + (!(feat_flags & RTE_CRYPTODEV_FF_SYM_RAW_DP))) {
> + printf("Device does not support RAW data-path APIs.\n");
> return TEST_SKIPPED;
> + }
>
> /* not supported with CPU crypto */
> if (gbl_action_type == RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO)
The first if() means that the next two are dead code, and that means
there is a log added that never gets printed. So need to remove
duplicate and decide on order of checks and whether you want the log.
prev parent reply other threads:[~2022-04-25 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 17:23 Kai Ji
2022-04-25 14:28 ` Kevin Traynor [this message]
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=faeeb57f-fa5f-0d1e-7e68-6c7030b42c82@redhat.com \
--to=ktraynor@redhat.com \
--cc=hemant.agrawal@nxp.com \
--cc=kai.ji@intel.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).