mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Maguire <alan.maguire@oracle.com>
To: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
	jolsa@kernel.org
Cc: kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
	john.fastabend@gmail.com, kpsingh@kernel.org,
	mhiramat@kernel.org, akpm@linux-foundation.org,
	void@manifault.com, swboyd@chromium.org, ndesaulniers@google.com,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	bpf@vger.kernel.org, Alan Maguire <alan.maguire@oracle.com>
Subject: [RFC bpf-next 0/2] bpf: add a kallsyms BPF iterator
Date: Fri, 24 Jun 2022 17:45:16 +0100	[thread overview]
Message-ID: <1656089118-577-1-git-send-email-alan.maguire@oracle.com> (raw)

a kallsyms BPF iterator would be useful as it would allow more flexible
iteractions with kernel symbols than are currently supported; it could
for example create more efficient map representations for lookup,
speed up symbol resolution etc.

The idea was initially discussed here [1].

[1] https://lore.kernel.org/all/YjRPZj6Z8vuLeEZo@krava/

Alan Maguire (2):
  bpf: add a kallsyms BPF iterator
  selftests/bpf: add a kallsyms iter subtest

 kernel/kallsyms.c                                  | 93 ++++++++++++++++++++++
 tools/testing/selftests/bpf/prog_tests/bpf_iter.c  | 16 ++++
 .../selftests/bpf/progs/bpf_iter_kallsyms.c        | 71 +++++++++++++++++
 3 files changed, 180 insertions(+)
 create mode 100644 tools/testing/selftests/bpf/progs/bpf_iter_kallsyms.c

-- 
1.8.3.1


             reply	other threads:[~2022-06-24 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-24 16:45 Alan Maguire [this message]
2022-06-24 16:45 ` [RFC bpf-next 1/2] " Alan Maguire
2022-06-24 22:18   ` Andrii Nakryiko
2022-06-24 16:45 ` [RFC bpf-next 2/2] selftests/bpf: add a kallsyms iter subtest 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=1656089118-577-1-git-send-email-alan.maguire@oracle.com \
    --to=alan.maguire@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kafai@fb.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=swboyd@chromium.org \
    --cc=void@manifault.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

all inboxes | Powered by JetHome®