From: patchwork-bot+netdevbpf@kernel.org
To: Yuho Choi <dbgh9129@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
kory.maincent@bootlin.com, zilin@seu.edu.cn,
arend.vanspriel@broadcom.com, marco.crivellari@suse.com,
u.kleine-koenig@baylibre.com, vadim.fedorenko@linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] net/liquidio: drop cached VF pci_dev LUT
Date: Tue, 07 Jul 2026 09:10:05 +0000 [thread overview]
Message-ID: <178341540539.1444421.11911347104966088843.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260701040847.1897845-1-dbgh9129@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Wed, 1 Jul 2026 00:08:47 -0400 you wrote:
> The PF SR-IOV enable path caches VF pci_dev pointers in
> dpiring_to_vfpcidev_lut[] by iterating with pci_get_device(). Those
> entries do not own a reference, because the iterator drops the previous
> device reference on each step. The cached pointer is then dereferenced
> later when handling OCTEON_VF_FLR_REQUEST.
>
> Replace the cached VF mapping with runtime lookup on the mailbox DPI
> ring: derive the VF index from q_no, resolve the VF via exported PCI
> IOV helpers, validate it with the PF pointer and VF ID, then issue
> pcie_flr() and drop the reference with pci_dev_put(). Remove the
> unused VF lookup table initialization and cleanup.
>
> [...]
Here is the summary with links:
- [v3] net/liquidio: drop cached VF pci_dev LUT
https://git.kernel.org/netdev/net/c/5c0e3ba4f500
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-07 9:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 4:08 [PATCH v3] net/liquidio: drop cached VF pci_dev LUT Yuho Choi
2026-07-07 9:10 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178341540539.1444421.11911347104966088843.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=arend.vanspriel@broadcom.com \
--cc=davem@davemloft.net \
--cc=dbgh9129@gmail.com \
--cc=edumazet@google.com \
--cc=kory.maincent@bootlin.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=u.kleine-koenig@baylibre.com \
--cc=vadim.fedorenko@linux.dev \
--cc=zilin@seu.edu.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox