From: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH net-next 5/5] ice: use debugfs to output FW log data
Date: Tue, 29 Nov 2022 13:28:27 -0800 [thread overview]
Message-ID: <56771e46-5f07-2e83-55cb-35bbddbcf49d@intel.com> (raw)
In-Reply-To: <e309ba9e-c908-5e09-c00a-a5dbf3c59f02@molgen.mpg.de>
On 11/29/2022 5:53 AM, Paul Menzel wrote:
> Dear Paul,
>
>
> Am 28.11.22 um 22:47 schrieb Paul M Stillwell Jr:
>> The FW log data can be quite large so we don't want to use syslog.
>> Instead take advantage of debugfs to write the data to.
>>
>> Also, a previous patch addded codde to disable FW logging when
>
> added code
>
Good catch, will fix.
>> the driver was unloaded. The code was added to
>> ice_devlink_unregister(), which didn't seem correct so move the
>> disabling of FW logging on driver unload to a better place.
>
> It’d be great if you added examples, how to get the log from debugfs,
> and decode(?) it.
>
Will do
>
> Kind regards,
>
> Paul
>
>
>> Signed-off-by: Paul M Stillwell Jr <paul.m.stillwell.jr@intel.com>
>> ---
>> drivers/net/ethernet/intel/ice/Makefile | 3 +-
>> drivers/net/ethernet/intel/ice/ice.h | 24 ++++
>> .../net/ethernet/intel/ice/ice_adminq_cmd.h | 2 +
>> drivers/net/ethernet/intel/ice/ice_debugfs.c | 109 ++++++++++++++++++
>> drivers/net/ethernet/intel/ice/ice_devlink.c | 20 ----
>> drivers/net/ethernet/intel/ice/ice_main.c | 98 ++++++++++++++++
>> 6 files changed, 235 insertions(+), 21 deletions(-)
>> create mode 100644 drivers/net/ethernet/intel/ice/ice_debugfs.c
>
> […]
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2022-11-29 21:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 21:47 [Intel-wired-lan] [PATCH net-next 0/5] add v2 FW logging for ice driver Paul M Stillwell Jr
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 1/5] ice: remove FW logging code Paul M Stillwell Jr
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 2/5] ice: enable devlink to check FW logging status Paul M Stillwell Jr
2022-12-01 0:39 ` Tony Nguyen
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 3/5] ice: add ability to query/set FW log level and resolution Paul M Stillwell Jr
2022-11-29 11:48 ` Wilczynski, Michal
2022-11-29 13:30 ` Alexander Lobakin
2022-11-29 21:31 ` Paul M Stillwell Jr
2022-12-01 0:39 ` Tony Nguyen
2022-12-09 0:00 ` Paul M Stillwell Jr
2022-12-01 7:36 ` Paul Menzel
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 4/5] ice: disable FW logging on driver unload Paul M Stillwell Jr
2022-11-29 12:05 ` Wilczynski, Michal
2022-11-29 21:31 ` Paul M Stillwell Jr
2022-12-01 0:40 ` Tony Nguyen
2022-11-28 21:47 ` [Intel-wired-lan] [PATCH net-next 5/5] ice: use debugfs to output FW log data Paul M Stillwell Jr
2022-11-29 13:53 ` Paul Menzel
2022-11-29 21:28 ` Paul M Stillwell Jr [this message]
2022-12-01 0:40 ` Tony Nguyen
2022-12-09 18:32 ` Paul M Stillwell Jr
2022-12-01 0:39 ` [Intel-wired-lan] [PATCH net-next 0/5] add v2 FW logging for ice driver 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=56771e46-5f07-2e83-55cb-35bbddbcf49d@intel.com \
--to=paul.m.stillwell.jr@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=pmenzel@molgen.mpg.de \
/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