From: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
To: "Dybkowski, AdamX" <adamx.dybkowski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"gakhil@marvell.com" <gakhil@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v4] test/crypto: check if RAW API is supported
Date: Tue, 20 Jul 2021 13:14:51 +0000 [thread overview]
Message-ID: <BL0PR11MB3043F94B47DEFB33E37F1122B8E29@BL0PR11MB3043.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210720131133.62869-1-adamx.dybkowski@intel.com>
> -----Original Message-----
> From: Dybkowski, AdamX <adamx.dybkowski@intel.com>
> Sent: Tuesday, July 20, 2021 2:12 PM
> To: dev@dpdk.org; Zhang, Roy Fan <roy.fan.zhang@intel.com>;
> gakhil@marvell.com
> Cc: Dybkowski, AdamX <adamx.dybkowski@intel.com>
> Subject: [PATCH v4] test/crypto: check if RAW API is supported
>
> This patch adds checking if RAW API is supported at the start
> of the test command "cryptodev_qat_raw_api_autotest".
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> ---
> app/test/test_cryptodev.c | 43
> ++++++++++++++++++++++++++++++++++++++-
> 1 file changed, 42 insertions(+), 1 deletion(-)
>
> diff --git a/app/test/test_cryptodev.c b/app/test/test_cryptodev.c
> index 31201d93e1..25778f464b 100644
> --- a/app/test/test_cryptodev.c
> +++ b/app/test/test_cryptodev.c
> @@ -14517,6 +14517,41 @@ run_cryptodev_testsuite(const char
> *pmd_name)
> return ret;
> }
>
> +static int
> +require_feature_flag(const char *pmd_name, uint64_t flag, const char
> *flag_name)
> +{
> + struct rte_cryptodev_info dev_info;
> + uint8_t i, nb_devs;
> + int driver_id;
> +
> + driver_id = rte_cryptodev_driver_id_get(pmd_name);
> + if (driver_id == -1) {
> + RTE_LOG(WARNING, USER1, "%s PMD must be loaded.\n",
> pmd_name);
> + return TEST_SKIPPED;
> + }
> +
> + nb_devs = rte_cryptodev_count();
> + if (nb_devs < 1) {
> + RTE_LOG(WARNING, USER1, "No crypto devices found?\n");
> + return TEST_SKIPPED;
> + }
> +
> + for (i = 0; i < nb_devs; i++) {
> + rte_cryptodev_info_get(i, &dev_info);
> + if (dev_info.driver_id == driver_id) {
> + if (!(dev_info.feature_flags & flag)) {
> + RTE_LOG(INFO, USER1, "%s not
> supported\n",
> + flag_name);
> + return TEST_SKIPPED;
> + }
> + return 0; /* found */
> + }
> + }
> +
> + RTE_LOG(INFO, USER1, "%s not supported\n", flag_name);
> + return TEST_SKIPPED;
> +}
> +
> static int
> test_cryptodev_qat(void)
> {
> @@ -14766,10 +14801,16 @@ test_cryptodev_bcmfs(void)
> static int
> test_cryptodev_qat_raw_api(void)
> {
> + static const char *pmd_name =
> RTE_STR(CRYPTODEV_NAME_QAT_SYM_PMD);
> int ret;
>
> + ret = require_feature_flag(pmd_name,
> RTE_CRYPTODEV_FF_SYM_RAW_DP,
> + "RAW API");
> + if (ret)
> + return ret;
> +
> global_api_test_type = CRYPTODEV_RAW_API_TEST;
> - ret =
> run_cryptodev_testsuite(RTE_STR(CRYPTODEV_NAME_QAT_SYM_PMD));
> + ret = run_cryptodev_testsuite(pmd_name);
> global_api_test_type = CRYPTODEV_API_TEST;
>
> return ret;
> --
> 2.25.1
Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
next prev parent reply other threads:[~2021-07-20 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 12:37 [dpdk-dev] [PATCH v3] " Adam Dybkowski
2021-07-19 15:25 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-20 13:11 ` [dpdk-dev] [PATCH v4] " Adam Dybkowski
2021-07-20 13:14 ` Zhang, Roy Fan [this message]
2021-07-20 20:48 ` Akhil Goyal
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=BL0PR11MB3043F94B47DEFB33E37F1122B8E29@BL0PR11MB3043.namprd11.prod.outlook.com \
--to=roy.fan.zhang@intel.com \
--cc=adamx.dybkowski@intel.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
/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).