DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hamdan Igbaria <hamdani@nvidia.com>
To: <hamdani@nvidia.com>, <viacheslavo@nvidia.com>,
	<thomas@monjalon.net>, <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Cc: <dev@dpdk.org>, <orika@nvidia.com>, <valex@nvidia.com>
Subject: [PATCH 5/5] net/mlx5: support HW steering debug dump
Date: Thu, 26 Jan 2023 18:03:09 +0200	[thread overview]
Message-ID: <20230126160309.584967-5-hamdani@nvidia.com> (raw)
In-Reply-To: <20230126160309.584967-1-hamdani@nvidia.com>

Add the ability for the DPDK apps to call
HW steering relevant debug data dump function.

Signed-off-by: Hamdan Igbaria <hamdani@nvidia.com>
---
 drivers/net/mlx5/mlx5_flow.c | 19 +++++++++++++------
 1 file changed, 13 insertions(+), 6 deletions(-)

diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
index f5e2831480..8e3da63299 100644
--- a/drivers/net/mlx5/mlx5_flow.c
+++ b/drivers/net/mlx5/mlx5_flow.c
@@ -9857,10 +9857,13 @@ mlx5_flow_dev_dump(struct rte_eth_dev *dev, struct rte_flow *flow_idx,
 #ifdef HAVE_IBV_FLOW_DV_SUPPORT
 		if (mlx5_flow_dev_dump_sh_all(dev, file, error))
 			return -EINVAL;
+
+		if (sh->config.dv_flow_en == 2)
+			return mlx5dr_debug_dump(priv->dr_ctx, file);
 #endif
 		return mlx5_devx_cmd_flow_dump(sh->fdb_domain,
-					sh->rx_domain,
-					sh->tx_domain, file);
+					       sh->rx_domain,
+					       sh->tx_domain, file);
 	}
 	/* dump one */
 	flow = mlx5_ipool_get(priv->flows[MLX5_FLOW_TYPE_GEN],
@@ -9878,10 +9881,14 @@ mlx5_flow_dev_dump(struct rte_eth_dev *dev, struct rte_flow *flow_idx,
 		if (!dh)
 			return -ENOENT;
 		if (dh->drv_flow) {
-			ret = mlx5_devx_cmd_flow_single_dump(dh->drv_flow,
-					file);
-			if (ret)
-				return -ENOENT;
+			if (sh->config.dv_flow_en == 2) {
+				return -ENOTSUP;
+			} else {
+				ret = mlx5_devx_cmd_flow_single_dump(dh->drv_flow,
+								     file);
+				if (ret)
+					return -ENOENT;
+			}
 		}
 		handle_idx = dh->next.next;
 	}
-- 
2.31.1


  parent reply	other threads:[~2023-01-26 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 16:03 [PATCH 1/5] net/mlx5/hws: fix alias_rtc_0 print location in " Hamdan Igbaria
2023-01-26 16:03 ` [PATCH 2/5] net/mlx5/hws: change STC array size to 32K Hamdan Igbaria
2023-01-26 16:03 ` [PATCH 3/5] net/mlx5/hws: support STC info dump Hamdan Igbaria
2023-01-26 16:03 ` [PATCH 4/5] net/mlx5/hws: support IP version matching for non relaxed Hamdan Igbaria
2023-01-26 16:03 ` Hamdan Igbaria [this message]
2023-02-02 16:02 ` [v2 1/5] net/mlx5/hws: fix alias_rtc_0 print location in debug dump Hamdan Igbaria
2023-02-02 16:02   ` [v2 2/5] net/mlx5/hws: change STC array size to 32K Hamdan Igbaria
2023-02-02 16:02   ` [v2 3/5] net/mlx5/hws: support STC info dump Hamdan Igbaria
2023-02-02 16:02   ` [v2 4/5] net/mlx5/hws: support IP version matching for non relaxed Hamdan Igbaria
2023-02-02 16:02   ` [v2 5/5] net/mlx5: support HW steering debug dump Hamdan Igbaria
2023-02-12 11:50   ` [v2 1/5] net/mlx5/hws: fix alias_rtc_0 print location in " Matan Azrad
2023-02-14  8:28   ` Raslan Darawsheh

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=20230126160309.584967-5-hamdani@nvidia.com \
    --to=hamdani@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=valex@nvidia.com \
    --cc=viacheslavo@nvidia.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).