From: Simon Horman <horms@kernel.org>
To: Petr Machata <petrm@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Ido Schimmel <idosch@nvidia.com>,
mlxsw@nvidia.com, Jiri Pirko <jiri@resnulli.us>,
Amit Cohen <amcohen@nvidia.com>
Subject: Re: [PATCH net 1/3] mlxsw: core: Unregister EMAD trap using FORWARD action
Date: Tue, 16 Apr 2024 15:33:38 +0100 [thread overview]
Message-ID: <20240416143338.GQ2320920@kernel.org> (raw)
In-Reply-To: <bb8f06c1644f0d3dfb3a488f625f27476d9b8a01.1713262810.git.petrm@nvidia.com>
On Tue, Apr 16, 2024 at 12:24:14PM +0200, Petr Machata wrote:
> From: Ido Schimmel <idosch@nvidia.com>
>
> The device's manual (PRM - Programmer's Reference Manual) classifies the
> trap that is used to deliver EMAD responses as an "event trap". Among
> other things, it means that the only actions that can be associated with
> the trap are TRAP and FORWARD (NOP).
>
> Currently, during driver de-initialization the driver unregisters the
> trap by setting its action to DISCARD, which violates the above
> guideline. Future firmware versions will prevent such misuses by
> returning an error. This does not prevent the driver from working, but
> an error will be printed to the kernel log during module removal /
> devlink reload:
>
> mlxsw_spectrum 0000:03:00.0: Reg cmd access status failed (status=7(bad parameter))
> mlxsw_spectrum 0000:03:00.0: Reg cmd access failed (reg_id=7003(hpkt),type=write)
>
> Suppress the error message by aligning the driver to the manual and use
> a FORWARD (NOP) action when unregistering the trap.
>
> Fixes: 4ec14b7634b2 ("mlxsw: Add interface to access registers and process events")
> Cc: Jiri Pirko <jiri@resnulli.us>
> Cc: Amit Cohen <amcohen@nvidia.com>
> Signed-off-by: Ido Schimmel <idosch@nvidia.com>
> Reviewed-by: Petr Machata <petrm@nvidia.com>
> Signed-off-by: Petr Machata <petrm@nvidia.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-04-16 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 10:24 [PATCH net 0/3] mlxsw: Fixes Petr Machata
2024-04-16 10:24 ` [PATCH net 1/3] mlxsw: core: Unregister EMAD trap using FORWARD action Petr Machata
2024-04-16 14:33 ` Simon Horman [this message]
2024-04-16 10:24 ` [PATCH net 2/3] mlxsw: core_env: Fix driver initialization with old firmware Petr Machata
2024-04-16 14:36 ` Simon Horman
2024-04-17 8:43 ` Ido Schimmel
2024-04-16 10:24 ` [PATCH net 3/3] mlxsw: pci: " Petr Machata
2024-04-16 14:33 ` Simon Horman
2024-04-17 4:18 ` Kalesh Anakkur Purayil
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=20240416143338.GQ2320920@kernel.org \
--to=horms@kernel.org \
--cc=amcohen@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@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).