public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Will Hawkins <hawkinsw@obs.cr>
To: binutils@sourceware.org
Cc: Will Hawkins <hawkinsw@obs.cr>
Subject: [PATCH 0/1] objdump: Add callx support for BPF CPU v1
Date: Fri,  9 Feb 2024 13:07:31 -0500	[thread overview]
Message-ID: <20240209180734.443763-1-hawkinsw@obs.cr> (raw)

Hello everyone!

First time patch submitter but longtime GNU enthusiast. Thank you for
all the work that you all do to maintain these vital pieces of software
for the community.

I am one of the maintainers of ubpf, a userspace eBPF runtime. As part
of the ISA standardization process at the IETF, Dave Thaler discovered
that clang is now emiting the callx instruction when targeting CPU
versions all the way back to v1. I know from Jose that gcc emits that
instruction in a special mode. 

There is a discussion at the ebpf-for-windows GitHub about adding callx
support to prevail (and other related tools):

https://github.com/microsoft/ebpf-for-windows/issues/3237

This patch adds the ability for objdump to decode the callx instruction
for ELF-encoded binaries targeting CPU v1 and greater.

I tried very hard to follow best practices for creating this patch
submission but I am sure that I did something wrong. Please let me know
what I can do differently or better.

Again, thank you for your effort maintaining these programs for the
community!

Sincerely,
Will

Will Hawkins (1):
  objdump: Add callx support for BPF CPU v1

 include/opcode/bpf.h | 2 +-
 opcodes/bpf-opc.c    | 2 ++
 sim/bpf/bpf-sim.c    | 4 ++++
 3 files changed, 7 insertions(+), 1 deletion(-)

-- 
2.43.0


             reply	other threads:[~2024-02-09 18:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-09 18:07 Will Hawkins [this message]
2024-02-09 18:07 ` [PATCH 1/1] " Will Hawkins
2024-02-10  4:47   ` Hans-Peter Nilsson
2024-02-10  6:13     ` Will Hawkins
2024-02-11 23:26       ` Will Hawkins
2024-02-12 17:01 ` [PATCH 0/1] " Nick Clifton

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=20240209180734.443763-1-hawkinsw@obs.cr \
    --to=hawkinsw@obs.cr \
    --cc=binutils@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).