netdev - Re: [PATCH v5 net-next 04/10] qed: implement devlink info request

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: <20200803142951.4c92f1ee@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Mon, 3 Aug 2020 14:29:51 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Igor Russkikh <irusskikh@...vell.com>
Cc:     <netdev@...r.kernel.org>, "David S . Miller" <davem@...emloft.net>,
        Ariel Elior <aelior@...vell.com>,
        Michal Kalderon <mkalderon@...vell.com>,
        Denis Bolotin <dbolotin@...vell.com>,
        Jiri Pirko <jiri@...nulli.us>,
        Alexander Lobakin <alobakin@...vell.com>,
        Michal Kalderon <michal.kalderon@...vell.com>
Subject: Re: [PATCH v5 net-next 04/10] qed: implement devlink info request

On Sun, 2 Aug 2020 13:08:28 +0300 Igor Russkikh wrote:
> Here we return existing fw & mfw versions, we also fetch device's
> serial number:
> 
> ~$ sudo ~/iproute2/devlink/devlink  dev info
> pci/0000:01:00.0:
>   driver qed
>   serial_number REE1915E44552

Just to confirm - this is not:

   * - ``board.serial_number``
     - Board serial number of the device.

       This is usually the serial number of the board, often available in
       PCI *Vital Product Data*.

>   versions:
>       running:
>         fw 8.42.2.0
>       stored:
>         fw.mgmt 8.52.10.0
> pci/0000:01:00.1:
>   driver qed
>   serial_number REE1915E44552
>   versions:
>       running:
>         fw 8.42.2.0
>       stored:
>         fw.mgmt 8.52.10.0
> 
> MFW and FW are different firmwares on device.
> Management is a firmware responsible for link configuration and
> various control plane features. Its permanent and resides in NVM.
> 
> Running FW (or fastpath FW) is an embedded microprogram implementing
> all the packet processing, offloads, etc. This FW is being loaded
> on each start by the driver from FW binary blob.

Sounds like you should use:

fw.app - Data path microcode controlling high-speed packet processing.

Rather than:

fw - Overall firmware version, often representing the collection of fw.mgmt, fw.app, etc.

All quotes from devlink-info.rst in the kernel sources.