From: Jedrzej Jagielski <jedrzej.jagielski@intel.com>
To: intel-wired-lan@lists.osuosl.org
Cc: anthony.l.nguyen@intel.com, netdev@vger.kernel.org,
Jedrzej Jagielski <jedrzej.jagielski@intel.com>
Subject: [PATCH iwl-next v1 0/2] i40e: Log FW state in recovery mode
Date: Fri, 12 Jan 2024 10:59:43 +0100 [thread overview]
Message-ID: <20240112095945.450590-1-jedrzej.jagielski@intel.com> (raw)
Introduce logging FW state in recovery mode functionality.
1st patch adds implementation of admin command reading content of alt
ram.
2nd patch utilices the command to get trace buffer data and logs it
when entering recovery mode.
Jedrzej Jagielski (1):
i40e-linux: Add support for reading Trace Buffer
Przemyslaw R Karpinski (1):
i40e: Add read alternate indirect command
drivers/net/ethernet/intel/i40e/i40e.h | 2 +
.../net/ethernet/intel/i40e/i40e_adminq_cmd.h | 4 +-
drivers/net/ethernet/intel/i40e/i40e_common.c | 40 +++++++++++++++++++
drivers/net/ethernet/intel/i40e/i40e_main.c | 35 ++++++++++++++++
.../net/ethernet/intel/i40e/i40e_prototype.h | 3 ++
.../net/ethernet/intel/i40e/i40e_register.h | 2 +
drivers/net/ethernet/intel/i40e/i40e_type.h | 5 +++
7 files changed, 89 insertions(+), 2 deletions(-)
--
2.31.1
next reply other threads:[~2024-01-12 10:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 9:59 Jedrzej Jagielski [this message]
2024-01-12 9:59 ` [PATCH iwl-next v1 1/2] i40e: Add read alternate indirect command Jedrzej Jagielski
2024-01-13 16:07 ` Simon Horman
2024-01-12 9:59 ` [PATCH iwl-next v1 2/2] i40e-linux: Add support for reading Trace Buffer Jedrzej Jagielski
2024-01-12 12:49 ` Jiri Pirko
2024-01-15 10:37 ` Jagielski, Jedrzej
2024-01-15 14:06 ` Jiri Pirko
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=20240112095945.450590-1-jedrzej.jagielski@intel.com \
--to=jedrzej.jagielski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).