From: Dave Jiang <dave.jiang@intel.com>
To: Koichiro Den <den@valinux.co.jp>,
Frank.Li@nxp.com, kishon@kernel.org, jdmason@kudzu.us,
mani@kernel.org, allenbh@gmail.com, kwilczynski@kernel.org,
bhelgaas@google.com, jbrunet@baylibre.com, lpieralisi@kernel.org
Cc: linux-pci@vger.kernel.org, ntb@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 09/10] NTB: epf: Fix doorbell bitmask handling in db_read/db_clear
Date: Wed, 25 Feb 2026 10:04:42 -0700 [thread overview]
Message-ID: <99bea052-80f4-4552-8e98-4b99094c8335@intel.com> (raw)
In-Reply-To: <20260224133459.1741537-10-den@valinux.co.jp>
On 2/24/26 6:34 AM, Koichiro Den wrote:
> The EPF driver currently stores the incoming doorbell as a vector number
> (irq_no + 1) in db_val and db_clear() clears all bits unconditionally.
> This breaks db_read()/db_clear() semantics when multiple doorbells are
> used.
>
> Store doorbells as a bitmask (BIT_ULL(vector)) and make
> db_clear(db_bits) clear only the specified bits. Use atomic64 operations
> as db_val is updated from interrupt context.
>
> Fixes: 812ce2f8d14e ("NTB: Add support for EPF PCI Non-Transparent Bridge")
> Signed-off-by: Koichiro Den <den@valinux.co.jp>
> ---
> drivers/ntb/hw/epf/ntb_hw_epf.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/ntb/hw/epf/ntb_hw_epf.c b/drivers/ntb/hw/epf/ntb_hw_epf.c
> index 00956ab2fbf5..0018adc35f16 100644
> --- a/drivers/ntb/hw/epf/ntb_hw_epf.c
> +++ b/drivers/ntb/hw/epf/ntb_hw_epf.c
> @@ -6,6 +6,7 @@
> * Author: Kishon Vijay Abraham I <kishon@ti.com>
> */
>
> +#include <linux/atomic.h>
> #include <linux/delay.h>
> #include <linux/module.h>
> #include <linux/pci.h>
> @@ -102,7 +103,7 @@ struct ntb_epf_dev {
> unsigned int self_spad;
> unsigned int peer_spad;
>
> - int db_val;
> + atomic64_t db_val;
> u64 db_valid_mask;
> };
>
> @@ -331,15 +332,16 @@ static irqreturn_t ntb_epf_vec_isr(int irq, void *dev)
> int irq_no;
>
> irq_no = irq - pci_irq_vector(ndev->ntb.pdev, 0);
> - ndev->db_val = irq_no + 1;
>
> if (irq_no == 0) {
> ntb_link_event(&ndev->ntb);
> } else if (irq_no == 1) {
> dev_warn_ratelimited(ndev->dev,
> "Unexpected irq_no 1 received. Treat it as DB#0.\n");
> + atomic64_or(BIT_ULL(0), &ndev->db_val);
> ntb_db_event(&ndev->ntb, 0);
> } else {
> + atomic64_or(BIT_ULL(irq_no - 2), &ndev->db_val);
Again here the bits probably can use a define or enum instead of magic numbers.
DJ
> ntb_db_event(&ndev->ntb, irq_no - 2);
> }
>
> @@ -524,7 +526,7 @@ static u64 ntb_epf_db_read(struct ntb_dev *ntb)
> {
> struct ntb_epf_dev *ndev = ntb_ndev(ntb);
>
> - return ndev->db_val;
> + return atomic64_read(&ndev->db_val);
> }
>
> static int ntb_epf_db_clear_mask(struct ntb_dev *ntb, u64 db_bits)
> @@ -536,7 +538,7 @@ static int ntb_epf_db_clear(struct ntb_dev *ntb, u64 db_bits)
> {
> struct ntb_epf_dev *ndev = ntb_ndev(ntb);
>
> - ndev->db_val = 0;
> + atomic64_and(~db_bits, &ndev->db_val);
>
> return 0;
> }
next prev parent reply other threads:[~2026-02-25 17:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 13:34 [PATCH 00/10] NTB: epf: Enable per-doorbell bit handling while keeping legacy offset Koichiro Den
2026-02-24 13:34 ` [PATCH 01/10] PCI: endpoint: pci-epf-vntb: Document legacy MSI doorbell offset Koichiro Den
2026-02-25 20:34 ` Frank Li
2026-02-24 13:34 ` [PATCH 02/10] PCI: endpoint: pci-epf-vntb: Defer pci_epc_raise_irq() out of atomic context Koichiro Den
2026-02-25 20:36 ` Frank Li
2026-02-26 1:02 ` Koichiro Den
2026-02-27 7:32 ` Koichiro Den
2026-02-24 13:34 ` [PATCH 03/10] PCI: endpoint: pci-epf-vntb: Report 0-based doorbell vector via ntb_db_event() Koichiro Den
2026-02-25 20:54 ` Frank Li
2026-02-24 13:34 ` [PATCH 04/10] PCI: endpoint: pci-epf-vntb: Exclude reserved slots from db_valid_mask Koichiro Den
2026-02-25 20:55 ` Frank Li
2026-02-24 13:34 ` [PATCH 05/10] PCI: endpoint: pci-epf-vntb: Implement db_vector_count/mask for doorbells Koichiro Den
2026-02-25 21:02 ` Frank Li
2026-02-27 6:23 ` Koichiro Den
2026-02-24 13:34 ` [PATCH 06/10] NTB: epf: Document legacy doorbell slot offset in ntb_epf_peer_db_set() Koichiro Den
2026-02-25 16:46 ` Dave Jiang
2026-02-25 21:03 ` Frank Li
2026-02-24 13:34 ` [PATCH 07/10] NTB: epf: Make db_valid_mask cover only real doorbell bits Koichiro Den
2026-02-25 16:47 ` Dave Jiang
2026-02-26 3:24 ` Koichiro Den
2026-02-25 21:07 ` Frank Li
2026-02-26 1:25 ` Koichiro Den
2026-02-24 13:34 ` [PATCH 08/10] NTB: epf: Report 0-based doorbell vector via ntb_db_event() Koichiro Den
2026-02-25 16:59 ` Dave Jiang
2026-02-26 3:17 ` Koichiro Den
2026-02-25 21:09 ` Frank Li
2026-02-24 13:34 ` [PATCH 09/10] NTB: epf: Fix doorbell bitmask handling in db_read/db_clear Koichiro Den
2026-02-25 17:04 ` Dave Jiang [this message]
2026-02-25 21:11 ` Frank Li
2026-02-24 13:34 ` [PATCH 10/10] NTB: epf: Implement db_vector_count/mask for doorbells Koichiro Den
2026-02-25 17:09 ` Dave Jiang
2026-02-25 21:13 ` Frank Li
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=99bea052-80f4-4552-8e98-4b99094c8335@intel.com \
--to=dave.jiang@intel.com \
--cc=Frank.Li@nxp.com \
--cc=allenbh@gmail.com \
--cc=bhelgaas@google.com \
--cc=den@valinux.co.jp \
--cc=jbrunet@baylibre.com \
--cc=jdmason@kudzu.us \
--cc=kishon@kernel.org \
--cc=kwilczynski@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=ntb@lists.linux.dev \
/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