[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACKFLimq7juLHbEs9gbuzRm7mFGvD62RsgrXdxr-fmj5e+zBbw@mail.gmail.com>
Date: Wed, 18 Dec 2024 22:57:09 -0800
From: Michael Chan <michael.chan@...adcom.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, andrew+netdev@...n.ch, pavan.chebbi@...adcom.com,
andrew.gospodarek@...adcom.com, Ajit Khaparde <ajit.khaparde@...adcom.com>,
Kalesh AP <kalesh-anakkur.purayil@...adcom.com>,
Somnath Kotur <somnath.kotur@...adcom.com>
Subject: Re: [PATCH net-next v2 5/6] bnxt_en: Skip reading PXP registers
during ethtool -d if unsupported
On Wed, Dec 18, 2024 at 7:13 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> On Tue, 17 Dec 2024 10:26:19 -0800 Michael Chan wrote:
> > Newer firmware does not allow reading the PXP registers during
> > ethtool -d, so skip the firmware call in that case. Userspace
> > (bnxt.c) always expects the register block to be populated so
> > zeroes will be returned instead.
>
> We have both the ability to return the number of registers (regs_len),
> and the regs->version. Are you sure you don't want to use either option
> to let user space know the regs aren't there?
The existing bnxt.c in userspace since 2020 always assumes that the
beginning part always contains the PXP register block regardless of
regs->version as long as the register length >= the length of the
register block. I guess we didn't anticipate that this PXP block
would ever be changed or FW would disallow reading it.
Download attachment "smime.p7s" of type "application/pkcs7-signature" (4209 bytes)
Powered by blists - more mailing lists