[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20260121201412.179f9b37@kernel.org>
Date: Wed, 21 Jan 2026 20:14:12 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Erni Sri Satya Vennela <ernis@...ux.microsoft.com>
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, wei.liu@...nel.org,
decui@...rosoft.com, longli@...rosoft.com, andrew+netdev@...n.ch,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
leon@...nel.org, kotaranov@...rosoft.com, shradhagupta@...ux.microsoft.com,
yury.norov@...il.com, dipayanroy@...ux.microsoft.com,
shirazsaleem@...rosoft.com, ssengar@...ux.microsoft.com,
gargaditya@...ux.microsoft.com, linux-hyperv@...r.kernel.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next v2] net: mana: Improve diagnostic logging for
better debuggability
On Tue, 20 Jan 2026 22:56:55 -0800 Erni Sri Satya Vennela wrote:
> Enhance MANA driver logging to provide better visibility into
> hardware configuration and error states during driver initialization
> and runtime operations.
> + dev_info(gc->dev, "Max Resources: msix_usable=%u max_queues=%u\n",
> + gc->num_msix_usable, gc->max_num_queues);
> + dev_info(dev, "Device Config: max_vports=%u adapter_mtu=%u bm_hostmode=%u\n",
> + *max_num_vports, gc->adapter_mtu, *bm_hostmode);
IIUC in networking we try to follow the mantra that if the system is
functioning correctly there should be no logs. You can expose the debug
info via ethtool, devlink, debugfs etc. Take your pick.
--
pw-bot: cr
Powered by blists - more mailing lists