netdev - Re: [PATCH net-next v2 3/3] octeontx2-af: add support for custom KPU entries

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20200921162643.6a52361d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Mon, 21 Sep 2020 16:26:43 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Stanislaw Kardach <skardach@...vell.com>
Cc:     <davem@...emloft.net>, <sgoutham@...vell.com>,
        <netdev@...r.kernel.org>, <kda@...ihalf.com>
Subject: Re: [PATCH net-next v2 3/3] octeontx2-af: add support for custom
 KPU entries

On Mon, 21 Sep 2020 19:54:42 +0200 Stanislaw Kardach wrote:
> Add ability to load a set of custom KPU entries via firmware APIs. This
> allows for flexible support for custom protocol parsing and CAM matching.
> 
> The firmware file name is specified by a module parameter (kpu_profile)
> to allow re-using the same kernel and initramfs package on nodes in
> different parts of the network where support for different protocols is
> required.
> 
> AF driver will attempt to load the profile from the firmware file and
> verify if it can fit hardware capabilities. If not, it will revert to
> the built-in profile.
> 
> Next it will read the maximum first KPU_MAX_CST_LT (2) custom entries
> from the firmware image. Those will be later programmed at the top of
> each KPU after the built-in profile entries have been programmed.
> The built-in profile is amended to always contain KPU_MAX_CSR_LT first
> no-match entries and AF driver will disable those in the KPU unless
> custom profile is loaded.

So the driver loads the firmware contents, interprets them and programs
the device appropriately?

Real firmware files are not usually interpreted or parsed by the driver.