netdev - RE: [PATCH iwl-next v2] ice: Disable Cage Max Power override

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <MW4PR11MB57768054635E8DEF841BB2A9FDE3A@MW4PR11MB5776.namprd11.prod.outlook.com>
Date: Fri, 25 Aug 2023 11:01:07 +0000
From: "Drewek, Wojciech" <wojciech.drewek@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>, "Kitszel, Przemyslaw"
	<przemyslaw.kitszel@...el.com>, "idosch@...dia.com" <idosch@...dia.com>
Subject: RE: [PATCH iwl-next v2] ice: Disable Cage Max Power override

CC: Ido

> -----Original Message-----
> From: Jakub Kicinski <kuba@...nel.org>
> Sent: czwartek, 24 sierpnia 2023 17:32
> To: Drewek, Wojciech <wojciech.drewek@...el.com>
> Cc: intel-wired-lan@...ts.osuosl.org; netdev@...r.kernel.org; Kitszel, Przemyslaw <przemyslaw.kitszel@...el.com>
> Subject: Re: [PATCH iwl-next v2] ice: Disable Cage Max Power override
> 
> On Thu, 24 Aug 2023 10:54:59 +0200 Wojciech Drewek wrote:
> > NVM module called "Cage Max Power override" allows to
> > change max power in the cage. This can be achieved
> > using external tools. The responsibility of the ice driver is to
> > go back to the default settings whenever port split is done.
> > This is achieved by clearing Override Enable bit in the
> > NVM module. Override of the max power is disabled so the
> > default value will be used.
> 
> Can you say more? We have ETHTOOL_MSG_MODULE_GET / SET, sounds like
> something we could quite easily get ethtool to support?

So you're suggesting that ethtool could support setting the maximum power in the cage? 
Something like:
 - new "--set-module" parameter called "power-max"
 - new "--get-module" parameters: "power-max-allowed", "power-min-allowed" indicating limitations reported by the HW.

About the patch itself, it's only about restoration of the default settings upon port split. Those might be overwritten by 
Intel's external tools.