From: Eduard Zingerman <eddyz87@gmail.com>
To: dwarves@vger.kernel.org
Cc: arnaldo.melo@gmail.com
Subject: [question] dwarves/pahole testing
Date: Thu, 23 Feb 2023 22:47:55 +0200 [thread overview]
Message-ID: <92b71fbfc8d768103d533d3b0edded0bd6750b0f.camel@gmail.com> (raw)
Hello Dwarves community,
I have a set of changes that add support for "btf_type_tag" attached to the
hosting type, as discussed in [1]. I'd like to test these changes before
submitting via this mailing list. I have some local tests for the feature
itself and I checked that kernel build / BPF selftests work as expected.
Are there any additional tests I can run?
Maybe some manual testing procedures?
Thanks,
Eduard
[1] https://github.com/eddyz87/dwarves
Dwarves update to support btf_type_tag:v2
[2] https://lore.kernel.org/bpf/87r0w9jjoq.fsf@oracle.com/
Discussion about update for btf_type_tag encoding in DWARF
next reply other threads:[~2023-02-23 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 20:47 Eduard Zingerman [this message]
2023-02-28 20:24 ` [question] dwarves/pahole testing Arnaldo Carvalho de Melo
2023-03-04 1:31 ` Eduard Zingerman
2023-03-04 2:13 ` Arnaldo Carvalho de Melo
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=92b71fbfc8d768103d533d3b0edded0bd6750b0f.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=arnaldo.melo@gmail.com \
--cc=dwarves@vger.kernel.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).