From: Simon Horman <horms@kernel.org>
To: Manish Awasthi <mawasthi@linux.microsoft.com>
Cc: netdev-bot+sashiko@kernel.org, kys@microsoft.com,
haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com,
longli@microsoft.com, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
kotaranov@microsoft.com, linux-hyperv@vger.kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, bpf@vger.kernel.org,
nipun.gupta@amd.com, nikhil.agarwal@amd.com,
gargaditya@linux.microsoft.com, ernis@linux.microsoft.com,
kees@kernel.org, paulros@microsoft.com, mawasthi@microsoft.com
Subject: Re: [PATCH net-next 4/4] net: mana: Add support for CDX device ID 0x00C2
Date: Tue, 29 Sep 2026 14:57:38 +0100 [thread overview]
Message-ID: <20260929135738.GT13925@horms.kernel.org> (raw)
In-Reply-To: <20260928202555.617331-1-mawasthi@linux.microsoft.com>
On Mon, Sep 28, 2026 at 08:25:55PM +0000, Manish Awasthi wrote:
> thanks for review. Comments inline.
>
> > Thank you for your contribution! Sashiko AI review found 3 potential
> > issue(s) to consider.
> >
> > Critical: 0 · High: 0 (1) · Medium: 1 · Low: 2
> >
> > If you believe none of the issues are legitimate, please reply to each
> > issue of Medium severity or higher and explain why the AI is wrong.
> > If any of them are legitimate and you plan to respin, please let patchwork
> > know by including "pw-bot: cr" as a separate line at the end of your reply
> > (one such reply per series is enough).
> >
> > - [Medium] The CDX transport installs `.dev_reset = mana_cdx_dev_reset`
> > (-> `cdx_dev_reset()`) but has no way to recover afterwards.
> > - [Low] `mana_cdx_setup_hwc_irqs()` skips IRQ affinity hints.
> > - [Low] The comment in `mana_gd_query_max_resources()` (gdma_main.c)
> > says: "Only reset on platforms that support dynamic MSI-X allocation;…
> >
> > Pre-existing issues:
> > - [High] This problem wasn't introduced by this patch, but the shared HWC
> > bootstrap path that the new CDX transport now reaches trusts a device-…
> >
> > --
> >
> > net: mana: Add support for CDX device ID 0x00C2
> >
> > This adds a CDX bus transport for MANA, built as mana_cdx.ko on top of
> > the shared gdma_core.ko, for device ID 0x00C2. It allocates the whole MSI
> > pool at probe time, limits the queue count to the available vectors,
> > restricts DMA to 32 bits, and adds a per-bus auxiliary device name prefix
> > so the CDX auxiliary devices stay separate from the PCI ones.
> >
> > > diff --git a/drivers/net/ethernet/microsoft/mana/gdma_cdx.c b/drivers/net/ethernet/microsoft/mana/gdma_cdx.c
> > > new file mode 100644
> > > index 0000000000000..0d01e3d2f0d96
> > > --- /dev/null
> > > +++ b/drivers/net/ethernet/microsoft/mana/gdma_cdx.c
> > > @@ -0,0 +1,340 @@
> >
> > [ ... ]
> >
> > > +static int mana_cdx_dev_reset(struct gdma_context *gc)
> > > +{
> > > + return cdx_dev_reset(gc->dev);
> > > +}
> >
> > [Severity: Medium]
> > Can this reset leave the whole function unusable, with no recovery short
> > of a manual rebind?
> >
> > mana_dealloc_queues() calls it when a TX queue still has pending_sends
> > after the drain timeout:
> >
> > mana_tx_timeout()
> > -> queue_reset_work
> > -> mana_per_port_queue_reset_work_handler()
> > -> mana_dealloc_queues()
> > -> mana_gd_dev_reset()
> > -> mana_cdx_dev_reset()
> > -> cdx_dev_reset()
> >
> This version of the driver doesn't support recovery after mana_cdx_dev_reset.
I don't think it needs to delay progress of this patchset.
But I am curious to know if there are plans to add such support.
...
next prev parent reply other threads:[~2026-09-29 13:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 17:30 [PATCH net-next 0/4] net: mana: Add support for the CDX bus Manish Awasthi
2026-09-24 17:30 ` [PATCH net-next 1/4] net: mana: Introduce gdma_bus_ops for bus-specific operations Manish Awasthi
2026-09-25 17:33 ` netdev-bot+sashiko
2026-09-28 19:16 ` Haiyang Zhang
2026-09-24 17:30 ` [PATCH net-next 2/4] net: mana: Move PCI transport code into gdma_pci.c Manish Awasthi
2026-09-25 17:33 ` netdev-bot+sashiko
2026-09-28 19:17 ` Haiyang Zhang
2026-09-24 17:30 ` [PATCH net-next 3/4] net: mana: Build the PCI transport as a separate module Manish Awasthi
2026-09-28 19:18 ` Haiyang Zhang
2026-09-24 17:30 ` [PATCH net-next 4/4] net: mana: Add support for CDX device ID 0x00C2 Manish Awasthi
2026-09-25 17:33 ` netdev-bot+sashiko
2026-09-28 20:25 ` Manish Awasthi
2026-09-29 13:57 ` Simon Horman [this message]
2026-09-29 23:45 ` Manish Awasthi
2026-09-28 19:18 ` Haiyang Zhang
2026-09-29 13:58 ` [PATCH net-next 0/4] net: mana: Add support for the CDX bus Simon Horman
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=20260929135738.GT13925@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=decui@microsoft.com \
--cc=edumazet@google.com \
--cc=ernis@linux.microsoft.com \
--cc=gargaditya@linux.microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=kees@kernel.org \
--cc=kotaranov@microsoft.com \
--cc=kuba@kernel.org \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=longli@microsoft.com \
--cc=mawasthi@linux.microsoft.com \
--cc=mawasthi@microsoft.com \
--cc=netdev-bot+sashiko@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=pabeni@redhat.com \
--cc=paulros@microsoft.com \
--cc=wei.liu@kernel.org \
/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
all inboxes | Powered by JetHome®