From: Shani Peretz <shperetz@nvidia.com>
To: <dev@dpdk.org>
Cc: <rasland@nvidia.com>, Shani Peretz <shperetz@nvidia.com>
Subject: [PATCH 0/2] Fix a doorbell race on Cortex-A78AE
Date: Sun, 22 Mar 2026 12:24:57 +0200 [thread overview]
Message-ID: <20260322102459.141958-1-shperetz@nvidia.com> (raw)
Fix a doorbell race on Cortex-A78AE where the compiler reorders a
64-bit WQE load before the 32-bit stores that construct it, causing
stale data to reach the hardware doorbell.
The first patch fixes the root cause by passing a pointer and adding
a compiler barrier;
The second patch reverts the crypto march extension workaround that is
no longer needed and that broke builds without AES support.
Shani Peretz (2):
common/mlx5: fix doorbell race from compiler reordering
config/arm: revert forced crypto extension for Cortex-A78AE
config/arm/meson.build | 7 ++-----
drivers/common/mlx5/mlx5_common.h | 12 ++++++++----
drivers/compress/mlx5/mlx5_compress.c | 2 +-
drivers/crypto/mlx5/mlx5_crypto_gcm.c | 6 +++---
drivers/crypto/mlx5/mlx5_crypto_xts.c | 2 +-
drivers/net/mlx5/mlx5_flow_aso.c | 12 ++++++------
drivers/net/mlx5/mlx5_flow_quota.c | 2 +-
drivers/net/mlx5/mlx5_rxq.c | 3 ++-
drivers/net/mlx5/mlx5_tx.h | 4 ++--
drivers/net/mlx5/mlx5_txpp.c | 4 ++--
drivers/regex/mlx5/mlx5_regex_fastpath.c | 2 +-
drivers/vdpa/mlx5/mlx5_vdpa_event.c | 2 +-
12 files changed, 30 insertions(+), 28 deletions(-)
--
2.34.1
next reply other threads:[~2026-03-22 10:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 10:24 Shani Peretz [this message]
2026-03-22 10:24 ` [PATCH 1/2] common/mlx5: fix doorbell race from compiler reordering Shani Peretz
2026-03-22 10:24 ` [PATCH 2/2] config/arm: revert forced crypto extension for Cortex-A78AE Shani Peretz
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=20260322102459.141958-1-shperetz@nvidia.com \
--to=shperetz@nvidia.com \
--cc=dev@dpdk.org \
--cc=rasland@nvidia.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