From: Alan Maguire <alan.maguire@oracle.com>
To: andrii@kernel.org, iii@linux.ibm.com, ast@kernel.org,
daniel@iogearbox.net
Cc: kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org,
netdev@vger.kernel.org, bpf@vger.kernel.org,
Alan Maguire <alan.maguire@oracle.com>
Subject: [PATCH bpf-next 0/2] libbpf: usdt aarch64 support
Date: Fri, 8 Apr 2022 23:52:44 +0100 [thread overview]
Message-ID: <1649458366-25288-1-git-send-email-alan.maguire@oracle.com> (raw)
USDT support [1] requires architecture-specific handling for translating
from argument strings describing each probe argument to appropriate values
that can be made available to the BPF program. Determining value size,
whether it refers to a dereference (and if there is an offset from the
register value), a register value or a constant all has to be parsed
slightly differently for different architectures.
However a common representation is created for use within BPF programs
(via usdt.bpf.h), and patch 1 abstracts out the initialization of
struct usdt_arg_spec associated with the argument, rather than repeating
those steps for each architecture.
Patch 2 then adds aarch64-specific argument parsing.
[1] https://lore.kernel.org/bpf/20220404234202.331384-1-andrii@kernel.org/
Alan Maguire (2):
libbpf: usdt: factor out common USDT arg handling
libbpf: usdt aarch64 arg parsing support
tools/lib/bpf/usdt.c | 134 +++++++++++++++++++++++++++++++++------------------
1 file changed, 87 insertions(+), 47 deletions(-)
--
1.8.3.1
next reply other threads:[~2022-04-08 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-08 22:52 Alan Maguire [this message]
2022-04-08 22:52 ` [PATCH bpf-next 1/2] libbpf: usdt: factor out common USDT arg handling Alan Maguire
2022-04-11 3:26 ` Andrii Nakryiko
2022-04-08 22:52 ` [PATCH bpf-next 2/2] libbpf: usdt aarch64 arg parsing support Alan Maguire
2022-04-11 4:11 ` Andrii Nakryiko
2022-04-11 7:56 ` Alan Maguire
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=1649458366-25288-1-git-send-email-alan.maguire@oracle.com \
--to=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=iii@linux.ibm.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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).