From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Brett Creeley <brett.creeley@amd.com>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <shannon.nelson@amd.com>
Subject: Re: [PATCH net-next 0/8] pds_core: Various improvements and AQ race condition cleanup
Date: Fri, 5 Jan 2024 08:59:53 +0100 [thread overview]
Message-ID: <ceb50c7c-b86a-422b-affe-e4a29e92fea7@intel.com> (raw)
In-Reply-To: <20240104171221.31399-1-brett.creeley@amd.com>
On 1/4/24 18:12, Brett Creeley wrote:
> There can be many users of the pds_core's adminq. This includes
> pds_core's uses and any clients that depend on it. When the pds_core
> device goes through a reset for any reason the adminq is freed
> and reconfigured. There are some gaps in the current implementation
> that will cause crashes during reset if any of the previously mentioned
> users of the adminq attempt to use it after it's been freed. This series
> addresses these issues.
>
> This series also includes some general cleanups.
>
> Brett Creeley (8):
> pds_core: Prevent health thread from running during reset/remove
> pds_core: Cancel AQ work on teardown
> pds_core: Use struct pdsc for the pdsc_adminq_isr private data
> pds_core: Prevent race issues involving the adminq
> pds_core: Clear BARs on reset
> pds_core: Don't assign interrupt index/bound_intr to notifyq
> pds_core: Unmask adminq interrupt in work thread
> pds_core: Fix up some RCT issues
>
> drivers/net/ethernet/amd/pds_core/adminq.c | 74 ++++++++++++++-------
> drivers/net/ethernet/amd/pds_core/core.c | 38 +++++++++--
> drivers/net/ethernet/amd/pds_core/core.h | 1 +
> drivers/net/ethernet/amd/pds_core/debugfs.c | 8 +--
> drivers/net/ethernet/amd/pds_core/dev.c | 9 ++-
> drivers/net/ethernet/amd/pds_core/devlink.c | 3 +-
> drivers/net/ethernet/amd/pds_core/fw.c | 3 +
> drivers/net/ethernet/amd/pds_core/main.c | 24 ++++++-
> 8 files changed, 123 insertions(+), 37 deletions(-)
>
very nice series, I didn't spot any problems with the code,
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
prev parent reply other threads:[~2024-01-05 8:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 17:12 [PATCH net-next 0/8] pds_core: Various improvements and AQ race condition cleanup Brett Creeley
2024-01-04 17:12 ` [PATCH net-next 1/8] pds_core: Prevent health thread from running during reset/remove Brett Creeley
2024-01-04 17:12 ` [PATCH net-next 2/8] pds_core: Cancel AQ work on teardown Brett Creeley
2024-01-04 17:12 ` [PATCH net-next 3/8] pds_core: Use struct pdsc for the pdsc_adminq_isr private data Brett Creeley
2024-01-04 17:12 ` [PATCH net-next 4/8] pds_core: Prevent race issues involving the adminq Brett Creeley
2024-01-04 19:16 ` Simon Horman
2024-01-04 19:24 ` Brett Creeley
2024-01-06 1:50 ` kernel test robot
2024-01-07 1:28 ` kernel test robot
2024-01-04 17:12 ` [PATCH net-next 5/8] pds_core: Clear BARs on reset Brett Creeley
2024-01-04 17:12 ` [PATCH net-next 6/8] pds_core: Don't assign interrupt index/bound_intr to notifyq Brett Creeley
2024-01-04 17:12 ` [PATCH net-next 7/8] pds_core: Unmask adminq interrupt in work thread Brett Creeley
2024-01-04 17:12 ` [PATCH net-next 8/8] pds_core: Fix up some RCT issues Brett Creeley
2024-01-05 7:59 ` Przemek Kitszel [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=ceb50c7c-b86a-422b-affe-e4a29e92fea7@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shannon.nelson@amd.com \
/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;
as well as URLs for NNTP newsgroup(s).