public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eli Cohen <elic@nvidia.com>
To: <mst@redhat.com>, <jasowang@redhat.com>,
	<linux-kernel@vger.kernel.org>,
	<virtualization@lists.linux-foundation.org>
Cc: <si-wei.liu@oracle.com>, <eperezma@redhat.com>, <lulu@redhat.com>,
	"Eli Cohen" <elic@nvidia.com>
Subject: [PATCH 0/7] vdpa/mlx5: Add debugfs subtree and fixes
Date: Sun, 13 Nov 2022 15:44:35 +0200	[thread overview]
Message-ID: <20221113134442.152695-1-elic@nvidia.com> (raw)

This series is a resend of previously sent patch list. It adds a few
fixes so I treat as a v0 of a new series.

It adds a kernel config param CONFIG_MLX5_VDPA_STEERING_DEBUG that when
eabled allows to read rx unicast and multicast counters per tagged or untagged traffic.

Examples:
$ cat /sys/kernel/debug/mlx5/mlx5_core.sf.1/vdpa-0/rx/untagged/mcast/packets
$ cat /sys/kernel/debug/mlx5/mlx5_core.sf.1/vdpa-0/rx/untagged/ucast/bytes


Eli Cohen (7):
  vdpa/mlx5: Fix rule forwarding VLAN to TIR
  vdpa/mlx5: Fix wrong mac address deletion
  vdpa/mlx5: Move some definitions to a new header file
  vdpa/mlx5: Add debugfs subtree
  vdpa/mlx5: Add RX counters to debugfs
  vdpa/mlx5: Avoid using reslock in event_handler
  vdpa/mlx5: Avoid overwriting CVQ iotlb

 drivers/vdpa/Kconfig               |  12 ++
 drivers/vdpa/mlx5/Makefile         |   2 +-
 drivers/vdpa/mlx5/core/mlx5_vdpa.h |   5 +-
 drivers/vdpa/mlx5/core/mr.c        |  44 ++---
 drivers/vdpa/mlx5/net/debug.c      | 152 ++++++++++++++++++
 drivers/vdpa/mlx5/net/mlx5_vnet.c  | 248 ++++++++++++++---------------
 drivers/vdpa/mlx5/net/mlx5_vnet.h  |  94 +++++++++++
 7 files changed, 411 insertions(+), 146 deletions(-)
 create mode 100644 drivers/vdpa/mlx5/net/debug.c
 create mode 100644 drivers/vdpa/mlx5/net/mlx5_vnet.h

-- 
2.38.1


             reply	other threads:[~2022-11-13 13:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 13:44 Eli Cohen [this message]
2022-11-13 13:44 ` [PATCH 1/7] vdpa/mlx5: Fix rule forwarding VLAN to TIR Eli Cohen
2022-11-14  4:38   ` Jason Wang
2022-11-14  6:44     ` Eli Cohen
2022-11-14  8:07       ` Michael S. Tsirkin
2022-11-14  8:58         ` Eli Cohen
2022-11-13 13:44 ` [PATCH 2/7] vdpa/mlx5: Fix wrong mac address deletion Eli Cohen
2022-11-14  4:40   ` Jason Wang
2022-11-13 13:44 ` [PATCH 3/7] vdpa/mlx5: Move some definitions to a new header file Eli Cohen
2022-11-14  4:41   ` Jason Wang
2022-11-13 13:44 ` [PATCH 4/7] vdpa/mlx5: Add debugfs subtree Eli Cohen
2022-11-14  4:42   ` Jason Wang
2022-11-13 13:44 ` [PATCH 5/7] vdpa/mlx5: Add RX counters to debugfs Eli Cohen
2022-11-14  7:26   ` Jason Wang
2022-11-14  8:51     ` Eli Cohen
2022-11-13 13:44 ` [PATCH 6/7] vdpa/mlx5: Avoid using reslock in event_handler Eli Cohen
2022-11-14  7:53   ` Jason Wang
2022-11-14  8:58     ` Eli Cohen
2022-11-23  4:00       ` Jason Wang
2022-11-24  4:04         ` Jason Wang
2022-11-13 13:44 ` [PATCH 7/7] vdpa/mlx5: Avoid overwriting CVQ iotlb Eli Cohen
2022-11-13 13:51 ` [PATCH 0/7] vdpa/mlx5: Add debugfs subtree and fixes Michael S. Tsirkin
2022-11-13 13:56   ` Eli Cohen
2022-11-13 13:57     ` Michael S. Tsirkin
2022-11-13 14:01       ` Eli Cohen

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=20221113134442.152695-1-elic@nvidia.com \
    --to=elic@nvidia.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lulu@redhat.com \
    --cc=mst@redhat.com \
    --cc=si-wei.liu@oracle.com \
    --cc=virtualization@lists.linux-foundation.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