public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Puranjay Mohan <puranjay12@gmail.com>
To: andrii@kernel.org, ast@kernel.org, daniel@iogearbox.net,
	martin.lau@linux.dev, song@kernel.org, yhs@fb.com,
	bpf@vger.kernel.org, memxor@gmail.com
Cc: Puranjay Mohan <puranjay12@gmail.com>
Subject: [PATCH bpf-next v3 0/2] libbpf: usdt arm arg parsing support
Date: Tue,  7 Mar 2023 12:04:38 +0000	[thread overview]
Message-ID: <20230307120440.25941-1-puranjay12@gmail.com> (raw)

This series add the support of the ARM architecture to libbpf USDT. This
involves implementing the parse_usdt_arg() function for ARM.

It was seen that the last part of parse_usdt_arg() is repeated for all architectures,
so, the first patch in this series refactors these functions and moved the post
processing to parse_usdt_spec()

Changes in V2[1] to V3:

- Use a tabular approach to find register offsets.
- Add the patch for refactoring parse_usdt_arg()

Puranjay Mohan (2):
  libbpf: refactor parse_usdt_arg() to re-use code
  libbpf: usdt arm arg parsing support

 tools/lib/bpf/usdt.c | 195 ++++++++++++++++++++++++++-----------------
 1 file changed, 118 insertions(+), 77 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-03-07 12:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07 12:04 Puranjay Mohan [this message]
2023-03-07 12:04 ` [PATCH bpf-next v3 1/2] libbpf: refactor parse_usdt_arg() to re-use code Puranjay Mohan
2023-03-07 12:04 ` [PATCH bpf-next v3 2/2] libbpf: usdt arm arg parsing support Puranjay Mohan
2023-03-07 23:41   ` Andrii Nakryiko
2023-03-08  5:01     ` Puranjay Mohan
2023-03-08 17:15       ` Andrii Nakryiko
2023-03-08 18:36         ` Puranjay Mohan
2023-03-07 23:40 ` [PATCH bpf-next v3 0/2] " patchwork-bot+netdevbpf

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=20230307120440.25941-1-puranjay12@gmail.com \
    --to=puranjay12@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=martin.lau@linux.dev \
    --cc=memxor@gmail.com \
    --cc=song@kernel.org \
    --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