[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230210202358.6a2e890b@kernel.org>
Date: Fri, 10 Feb 2023 20:23:58 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Tony Nguyen <anthony.l.nguyen@...el.com>
Cc: davem@...emloft.net, pabeni@...hat.com, edumazet@...gle.com,
netdev@...r.kernel.org, paul.m.stillwell.jr@...el.com,
jacob.e.keller@...el.com, jiri@...dia.com, idosch@...sch.org
Subject: Re: [PATCH net-next 0/5][pull request] add v2 FW logging for ice
driver
Can you describe how this is used a little bit?
The FW log is captured at some level always (e.g. warns)
or unless user enables _nothing_ will come out?
On Thu, 9 Feb 2023 11:06:57 -0800 Tony Nguyen wrote:
> devlink dev param set <pci dev> name fwlog_enabled value <true/false> cmode runtime
> devlink dev param set <pci dev> name fwlog_level value <0-4> cmode runtime
> devlink dev param set <pci dev> name fwlog_resolution value <1-128> cmode runtime
If you're using debugfs as a pipe you should put these enable knobs
in there as well. Or add a proper devlink command to carry all this
information via structured netlink (fw log + level + enable are hardly
Intel specific).
Powered by blists - more mailing lists