Linux Documentation
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: "illusion.wang" <illusion.wang@nebula-matrix.com>,
	dimon.zhao@nebula-matrix.com, alvin.wang@nebula-matrix.com,
	sam.chen@nebula-matrix.com, netdev@vger.kernel.org
Cc: andrew+netdev@lunn.ch, corbet@lwn.net, kuba@kernel.org,
	horms@kernel.org, linux-doc@vger.kernel.org,
	vadim.fedorenko@linux.dev, lukas.bulwahn@redhat.com,
	edumazet@google.com, enelsonmoore@gmail.com,
	skhan@linuxfoundation.org, hkallweit1@gmail.com,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v17 net-next 07/11] net/nebula-matrix: add intr resource implementation
Date: Thu, 4 Jun 2026 12:23:00 +0200	[thread overview]
Message-ID: <a0178564-a7a2-46d8-afc0-636f027c31b6@redhat.com> (raw)
In-Reply-To: <20260601093149.25905-8-illusion.wang@nebula-matrix.com>

On 6/1/26 11:31 AM, illusion.wang wrote:
> This patch adds the nbl_interrupt module for management of driver-private
> MSI-X indices, plus hw_ops callbacks to program the function MSI-X mapping
> registers, configure MSI-X info, and enable mailbox interrupts.
> 
> Key interfaces:
> - configure_msix_map:   Allocates driver-private global MSI-X indices
>                           (interrupt_net_bitmap / interrupt_others_bitmap)
>                           and programs the hardware MSI-X mapping registers
>                           (NBL_PCOMPLETER_FUNCTION_MSIX_MAP).
>                           The actual PCI MSI-X vector allocation is done
>                           by nbl_dev_alloc_msix_intr().
> - destroy_msix_map:     Releases MSI-X indices and tears down the mapping.
> - set_mailbox_irq:       Enables/disables a specific mailbox interrupt.
> - configure_msix_info:   Programs PADPT_HOST_MSIX_INFO and
>                           PCOMPLETER_HOST_MSIX_FID_TABLE.
> 
> The patch does not use kernel MSI-X allocation primitives
> (pci_alloc_irq_vectors, pci_msix_alloc_irq_at, irq_domain). It manages
> a driver-private global index space and programs vendor-specific
> MSI-X mapping registers.
> 
> Note: Mutual exclusion for configure_msix_map, destroy_msix_map, and
> enable_mailbox_irq is handled by the dispatch layer; these functions
> assume the caller already holds the necessary lock.

Adding assertion based on mutex_is_locked() would make the above obvious
and will prevent locking issues.

/P


  reply	other threads:[~2026-06-04 10:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-01  9:31 [PATCH v17 net-next 00/11] nbl driver for Nebulamatrix NICs illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 01/11] net/nebula-matrix: add minimum nbl build framework illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 02/11] net/nebula-matrix: add our driver architecture illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 03/11] net/nebula-matrix: add chip related definitions illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 04/11] net/nebula-matrix: channel msg value and msg struct illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 05/11] net/nebula-matrix: add channel layer illusion.wang
2026-06-04 10:18   ` Paolo Abeni
2026-06-05  2:00     ` 回复:[PATCH " Illusion Wang
2026-06-01  9:31 ` [PATCH v17 net-next 06/11] net/nebula-matrix: add common resource implementation illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 07/11] net/nebula-matrix: add intr " illusion.wang
2026-06-04 10:23   ` Paolo Abeni [this message]
2026-06-01  9:31 ` [PATCH v17 net-next 08/11] net/nebula-matrix: add vsi " illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 09/11] net/nebula-matrix: add Dispatch layer implementation illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 10/11] net/nebula-matrix: add common/ctrl dev init/reinit operation illusion.wang
2026-06-01  9:31 ` [PATCH v17 net-next 11/11] net/nebula-matrix: add common dev start/stop operation illusion.wang

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=a0178564-a7a2-46d8-afc0-636f027c31b6@redhat.com \
    --to=pabeni@redhat.com \
    --cc=alvin.wang@nebula-matrix.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=corbet@lwn.net \
    --cc=dimon.zhao@nebula-matrix.com \
    --cc=edumazet@google.com \
    --cc=enelsonmoore@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=horms@kernel.org \
    --cc=illusion.wang@nebula-matrix.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.bulwahn@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=sam.chen@nebula-matrix.com \
    --cc=skhan@linuxfoundation.org \
    --cc=vadim.fedorenko@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