Re: [PATCH v4 00/12] PCI: endpoint: pci-epf-vntb / NTB: epf: Enable per-doorbell bit handling
From: Manivannan Sadhasivam
Date: Wed May 27 2026 - 05:09:20 EST
On Wed, 13 May 2026 11:49:11 +0900, Koichiro Den wrote:
> This series fixes doorbell bit/vector handling for the EPF-based NTB
> pair (ntb_hw_epf <-> pci-epf-*ntb). Its primary goal is to enable safe
> per-db-vector handling in the NTB core and clients (e.g. ntb_transport),
> without changing the on-the-wire doorbell mapping.
>
>
> Background / problem
> ====================
>
> [...]
Applied, thanks!
[01/12] PCI: endpoint: pci-epf-vntb: Document legacy MSI doorbell offset
commit: 683f8a747ab35886cc9bef96025712011309eae5
[02/12] PCI: endpoint: pci-epf-vntb: Defer pci_epc_raise_irq() out of atomic context
commit: 84dd5950df2f540e52bd6cbcb5682cb4dff5f2a5
[03/12] PCI: endpoint: pci-epf-vntb: Report 0-based doorbell vector via ntb_db_event()
commit: 7c54a7152588e8892a7f7f2c69117f00c1bf24f4
[04/12] PCI: endpoint: pci-epf-vntb: Reject unusable doorbell counts
commit: 86b48f07a5a398ce1cd88e2f06ddab52c2181df0
[05/12] PCI: endpoint: pci-epf-vntb: Guard configfs writes after EPC attach
commit: 9da8fecbe9173cc1d48667b2b821e4d1f383edbb
[06/12] PCI: endpoint: pci-epf-vntb: Exclude reserved slots from db_valid_mask
commit: 12f666206720cb462ac4eaeb61a03e492737e1ef
[07/12] PCI: endpoint: pci-epf-vntb: Implement db_vector_count/mask for doorbells
commit: d7eacad42e2d812872fc7da83466657b7759dde1
[08/12] NTB: epf: Document legacy doorbell slot offset in ntb_epf_peer_db_set()
commit: d3de5eb64ecd836160afad84aa3ff639acb489cb
[09/12] NTB: epf: Make db_valid_mask cover only real doorbell bits
commit: 615dc10082a96423743d3a7b8b90eed80580916d
[10/12] NTB: epf: Report 0-based doorbell vector via ntb_db_event()
commit: c8220ccb30e8c092db9b6fa7dcb06dfd5340457d
[11/12] NTB: epf: Fix doorbell bitmask and IRQ vector handling
commit: 1c981bf355e8ab78c45717fbd322bd67fafa8082
[12/12] NTB: epf: Implement db_vector_count/mask for doorbells
commit: e6ff30150738af5c7aa20fad08b74cbf9b86d3a2
Best regards,
--
Manivannan Sadhasivam <mani@xxxxxxxxxx>