netdev - Re: [PATCH net v2 1/1] bnx2x: Assign unique DMAE channel number for FW DMAE transactions.

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] [day] [month] [year] [list]

Message-Id: <20181112.085455.1513459403088791878.davem@davemloft.net>
Date:   Mon, 12 Nov 2018 08:54:55 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     sudarsana.kalluru@...ium.com
Cc:     netdev@...r.kernel.org, Michal.Kalderon@...ium.com
Subject: Re: [PATCH net v2 1/1] bnx2x: Assign unique DMAE channel number
 for FW DMAE transactions.

From: Sudarsana Reddy Kalluru <sudarsana.kalluru@...ium.com>
Date: Sun, 11 Nov 2018 18:27:34 -0800

> Driver assigns DMAE channel 0 for FW as part of START_RAMROD command. FW
> uses this channel for DMAE operations (e.g., TIME_SYNC implementation).
> Driver also uses the same channel 0 for DMAE operations for some of the PFs
> (e.g., PF0 on Port0). This could lead to concurrent access to the DMAE
> channel by FW and driver which is not legal. Hence need to assign unique
> DMAE id for FW.
> Currently following DMAE channels are used by the clients,
>   MFW - OCBB/OCSD functionality uses DMAE channel 14/15
>   Driver 0-3 and 8-11 (for PF dmae operations)
>          4 and 12 (for stats requests)
> Assigning unique dmae_id '13' to the FW.
> 
> Changes from previous version:
> ------------------------------
> v2: Incorporated the review comments.
> 
> Signed-off-by: Sudarsana Reddy Kalluru <Sudarsana.Kalluru@...ium.com>
> Signed-off-by: Michal Kalderon <Michal.Kalderon@...ium.com>

Applied.