From: Vikas Gupta <vikas.gupta@broadcom.com>
To: jiri@nvidia.com, kuba@kernel.org
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, dsahern@kernel.org,
stephen@networkplumber.org, edumazet@google.com,
michael.chan@broadcom.com, andrew.gospodarek@broadcom.com,
Vikas Gupta <vikas.gupta@broadcom.com>
Subject: [PATCH net-next v1 0/3] add framework for selftests in devlink
Date: Tue, 28 Jun 2022 22:12:38 +0530 [thread overview]
Message-ID: <20220628164241.44360-1-vikas.gupta@broadcom.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1345 bytes --]
Hi,
This patchset adds support for selftests in the devlink framework.
It adds a callback .selftests_show and .selftests_run in devlink_ops.
User can provide test(s) suite as a testmask and subsequently it is passed
to the driver which can opt for running particular tests based on
its capabilities.
Patchset adds a flash based test for the bnxt_en driver.
Suggested commands at user level would be as below:
$ devlink dev selftests run pci/0000:03:00.0 test flash
results:
flash test : failed
$ devlink dev selftests show pci/0000:03:00.0
device suuports:
flash test
Thanks,
Vikas
Vikas Gupta (3):
devlink: introduce framework for selftests
bnxt_en: refactor NVM APIs
bnxt_en: implement callbacks for devlink selftests
.../networking/devlink/devlink-selftests.rst | 39 +++++
.../net/ethernet/broadcom/bnxt/bnxt_devlink.c | 66 ++++++++
.../net/ethernet/broadcom/bnxt/bnxt_ethtool.c | 24 +--
.../net/ethernet/broadcom/bnxt/bnxt_ethtool.h | 12 ++
include/net/devlink.h | 40 +++++
include/uapi/linux/devlink.h | 24 +++
net/core/devlink.c | 147 ++++++++++++++++++
7 files changed, 340 insertions(+), 12 deletions(-)
create mode 100644 Documentation/networking/devlink/devlink-selftests.rst
--
2.31.1
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4206 bytes --]
next reply other threads:[~2022-06-28 16:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 16:42 Vikas Gupta [this message]
2022-06-28 16:42 ` [PATCH net-next v1 1/3] devlink: introduce framework for selftests Vikas Gupta
2022-06-29 5:05 ` Jakub Kicinski
2022-06-28 16:42 ` [PATCH net-next v1 2/3] bnxt_en: refactor NVM APIs Vikas Gupta
2022-06-28 16:42 ` [PATCH net-next v1 3/3] bnxt_en: implement callbacks for devlink selftests Vikas Gupta
2022-07-07 18:29 ` [PATCH net-next v2 0/3] add framework for selftests in devlink Vikas Gupta
2022-07-07 18:29 ` [PATCH net-next v2 1/3] devlink: introduce framework for selftests Vikas Gupta
2022-07-08 1:20 ` Jakub Kicinski
2022-07-10 9:00 ` Ido Schimmel
2022-07-08 8:04 ` kernel test robot
2022-07-08 14:48 ` kernel test robot
2022-07-11 12:40 ` Jiri Pirko
[not found] ` <CAHLZf_t9ihOQPvcQa8cZsDDVUX1wisrBjC30tHG_-Dz13zg=qQ@mail.gmail.com>
2022-07-12 6:28 ` Jiri Pirko
2022-07-12 16:41 ` Vikas Gupta
2022-07-12 18:08 ` Jiri Pirko
2022-07-13 6:40 ` Vikas Gupta
2022-07-13 7:28 ` Jiri Pirko
2022-07-13 10:16 ` Vikas Gupta
2022-07-13 10:22 ` Jiri Pirko
2022-07-07 18:29 ` [PATCH net-next v2 2/3] bnxt_en: refactor NVM APIs Vikas Gupta
2022-07-07 18:29 ` [PATCH net-next v2 3/3] bnxt_en: implement callbacks for devlink selftests Vikas Gupta
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=20220628164241.44360-1-vikas.gupta@broadcom.com \
--to=vikas.gupta@broadcom.com \
--cc=andrew.gospodarek@broadcom.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.