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]
Date: Wed, 20 Mar 2024 10:50:29 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Subbaraya Sundeep <sbhatta@...vell.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org, davem@...emloft.net,
 edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
 sgoutham@...vell.com, lcherian@...vell.com, gakula@...vell.com,
 hkelam@...vell.com, naveenm@...vell.com, horms@...nel.org
Subject: Re: [v2 net PATCH 0/5] octeontx2-pf: RVU Mailbox fixes

Hello:

This series was applied to netdev/net.git (main)
by David S. Miller <davem@...emloft.net>:

On Mon, 18 Mar 2024 14:59:53 +0530 you wrote:
> This patchset fixes the problems related to RVU mailbox.
> During long run tests some times VF commands like setting
> MTU or toggling interface fails because VF mailbox is timedout
> waiting for response from PF.
> 
> Below are the fixes
> Patch 1: There are two types of messages in RVU mailbox namely up and down
> messages. Down messages are synchronous messages where a PF/VF sends
> a message to AF and AF replies back with response. UP messages are
> notifications and are asynchronous like AF sending link events to
> PF. When VF sends a down message to PF, PF forwards to AF and sends
> the response from AF back to VF. PF has to forward VF messages since
> there is no path in hardware for VF to send directly to AF.
> There is one mailbox interrupt from AF to PF when raised could mean
> two scenarios one is where AF sending reply to PF for a down message
> sent by PF and another one is AF sending up message asynchronously
> when link changed for that PF. Receiving the up message interrupt while
> PF is in middle of forwarding down message causes mailbox errors.
> Fix this by receiver detecting the type of message from the mbox data register
> set by sender.
> 
> [...]

Here is the summary with links:
  - [v2,net,1/5] octeontx2: Detect the mbox up or down message via register
    https://git.kernel.org/netdev/net/c/a88e0f936ba9
  - [v2,net,2/5] octeontx2-pf: Wait till detach_resources msg is complete
    https://git.kernel.org/netdev/net/c/cbf2f24939a5
  - [v2,net,3/5] octeontx2-pf: Use default max_active works instead of one
    https://git.kernel.org/netdev/net/c/7558ce0d974c
  - [v2,net,4/5] octeontx2-pf: Send UP messages to VF only when VF is up.
    https://git.kernel.org/netdev/net/c/dfcf6355f53b
  - [v2,net,5/5] octeontx2-af: Use separate handlers for interrupts
    https://git.kernel.org/netdev/net/c/50e60de381c3

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ