DPDK patches and discussions
 help / color / mirror / Atom feed
From: Marat Khalili <marat.khalili@huawei.com>
To: <dev@dpdk.org>
Subject: [PATCH v2 0/2] bpf: add xchg and fix rte_bpf_dump
Date: Thu, 18 Dec 2025 17:09:11 +0000	[thread overview]
Message-ID: <20251218170914.7737-1-marat.khalili@huawei.com> (raw)
In-Reply-To: <20251217172037.59170-1-marat.khalili@huawei.com>

Two patches that are not exectly functionally related, but one depends
on the other code-wise.

Atomic exchange is particularly useful since it can be used not just for
exchange per se, but also as atomic store.

Incidentally it was discovered that rte_bpf_dump does not support not
just atomics but also some other instructions.

v2: Fix CI failure: do not assume in tests that all platforms have JIT.

Marat Khalili (2):
  bpf: add atomic xchg support
  bpf: dump additional instructions

 app/test/test_bpf.c     | 459 ++++++++++++++++++++++++++++++++++++++++
 lib/bpf/bpf_def.h       |   5 +
 lib/bpf/bpf_dump.c      |  69 ++++--
 lib/bpf/bpf_exec.c      |  35 ++-
 lib/bpf/bpf_jit_arm64.c |  59 ++++--
 lib/bpf/bpf_jit_x86.c   |  37 +++-
 lib/bpf/bpf_validate.c  |  22 +-
 7 files changed, 637 insertions(+), 49 deletions(-)

-- 
2.43.0


  parent reply	other threads:[~2025-12-18 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 17:20 [PATCH " Marat Khalili
2025-12-17 17:20 ` [PATCH 1/2] bpf: add atomic xchg support Marat Khalili
2025-12-17 17:20 ` [PATCH 2/2] bpf: dump additional instructions Marat Khalili
2025-12-18 17:09 ` Marat Khalili [this message]
2025-12-18 17:09   ` [PATCH v2 1/2] bpf: add atomic xchg support Marat Khalili
2025-12-19 13:03     ` Konstantin Ananyev
2025-12-18 17:09   ` [PATCH v2 2/2] bpf: dump additional instructions Marat Khalili
2025-12-19 13:04     ` Konstantin Ananyev

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=20251218170914.7737-1-marat.khalili@huawei.com \
    --to=marat.khalili@huawei.com \
    --cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).