From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Konrad Knitter <konrad.knitter@intel.com>
Cc: Brett Creeley <brett.creeley@amd.com>,
<anthony.l.nguyen@intel.com>, <netdev@vger.kernel.org>,
<kuba@kernel.org>, <pabeni@redhat.com>, <dumazet@google.com>,
<davem@davemloft.net>, <andrew+netdev@lunn.ch>,
"Sharon Haroni" <sharon.haroni@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1] ice: fw and port health status
Date: Mon, 18 Nov 2024 12:58:53 +0100 [thread overview]
Message-ID: <1c737424-7f27-4318-8959-69bde80ceed0@intel.com> (raw)
In-Reply-To: <20241118104810.477794-1-konrad.knitter@intel.com>
On 11/18/24 11:48, Konrad Knitter wrote:
> Firmware generates events for global events or port specific events.
>
> Driver shall subscribe for health status events from firmware on supported
> FW versions >= 1.7.6.
> Driver shall expose those under specific health reporter, two new
> reporters are introduced:
> - FW health reporter shall represent global events (problems with the
> image, recovery mode);
> - Port health reporter shall represent port-specific events (module
> failure).
>
> Firmware only reports problems when those are detected, it does not store
> active fault list.
> Driver will hold only last global and last port-specific event.
> Driver will report all events via devlink health report,
> so in case of multiple events of the same source they can be reviewed
> using devlink autodump feature.
>
> $ devlink health
>
> pci/0000:b1:00.3:
> reporter fw
> state healthy error 0 recover 0 auto_dump true
> reporter port
> state error error 1 recover 0 last_dump_date 2024-03-17
> last_dump_time 09:29:29 auto_dump true
>
> $ devlink health diagnose pci/0000:b1:00.3 reporter port
>
> Syndrome: 262
> Description: Module is not present.
> Possible Solution: Check that the module is inserted correctly.
> Port Number: 0
>
> Tested on Intel Corporation Ethernet Controller E810-C for SFP
>
> Co-developed-by: Sharon Haroni <sharon.haroni@intel.com>
> Signed-off-by: Sharon Haroni <sharon.haroni@intel.com>
> Co-developed-by: Nicholas Nunley <nicholas.d.nunley@intel.com>
> Signed-off-by: Nicholas Nunley <nicholas.d.nunley@intel.com>
> Co-developed-by: Brett Creeley <brett.creeley@amd.com>
> Signed-off-by: Brett Creeley <brett.creeley@amd.com>
Brett signed-off as an Intel employee, and this should not be modified.
But it's very good that you have CC'd the new address.
> Signed-off-by: Konrad Knitter <konrad.knitter@intel.com>
There is no mention that this depends on my series, still in Tony's
queue.
> ---
> .../net/ethernet/intel/ice/devlink/health.c | 290 +++++++++++++++++-
> .../net/ethernet/intel/ice/devlink/health.h | 12 +
> .../net/ethernet/intel/ice/ice_adminq_cmd.h | 87 ++++++
> drivers/net/ethernet/intel/ice/ice_common.c | 37 +++
> drivers/net/ethernet/intel/ice/ice_common.h | 2 +
> drivers/net/ethernet/intel/ice/ice_main.c | 3 +
> drivers/net/ethernet/intel/ice/ice_type.h | 5 +
> 7 files changed, 429 insertions(+), 7 deletions(-)
Weirdly I find it nice for review despite the size, at least
in a way that I think it's actually good enough when not split into
multiple patches.
next prev parent reply other threads:[~2024-11-18 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 10:48 [Intel-wired-lan] [PATCH iwl-next v1] ice: fw and port health status Konrad Knitter
2024-11-18 11:58 ` Przemek Kitszel [this message]
2024-11-22 19:33 ` Tony Nguyen
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=1c737424-7f27-4318-8959-69bde80ceed0@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=dumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=konrad.knitter@intel.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sharon.haroni@intel.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