From: Alan Maguire <alan.maguire@oracle.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <olsajiri@gmail.com>
Cc: Eduard Zingerman <eddyz87@gmail.com>,
Viktor Malik <vmalik@redhat.com>,
dwarves@vger.kernel.org
Subject: Re: HEADS UP: pahole 1.26 to be released soon
Date: Wed, 28 Feb 2024 13:54:29 +0000 [thread overview]
Message-ID: <39f96bb5-5285-418f-a2b3-0142ffbea23a@oracle.com> (raw)
In-Reply-To: <Zd8oR11yexremMWp@x1>
On 28/02/2024 12:34, Arnaldo Carvalho de Melo wrote:
> On Wed, Feb 28, 2024 at 09:30:31AM +0100, Jiri Olsa wrote:
>> On Tue, Feb 27, 2024 at 09:59:14AM -0300, Arnaldo Carvalho de Melo wrote:
>>> If you have time, please do some tests and report results.
>>> You can find it in the usual places:
>>> git://git.kernel.org/pub/scm/devel/pahole/pahole.git
>>> https://github.com/acmel/dwarves.git
>>> In the master branch.
>
>> hi,
>> tested on top of my setup and it looks good
>
> Thanks!
>
Ditto here; tested on x86_64 and aarch64, all looks good.
>> I hoped the kfuncs decl tag would get in, but AFAICS there was
>> no new version of the patches.. I'll ping Daniel about that
>
> There is this global variables case that is being discussed, the kfuncs
> and I hope to do some work on .dwz, merging what I have at:
>
> https://git.kernel.org/pub/scm/devel/pahole/pahole.git/log/?h=alt_dwarf
>
> So I think I'll go ahead and release 1.26 today and work on merging
> these other features to have 1.27 in the near future.
>
Sounds great, thanks! I've been looking into reducing the memory
footprint during pahole operation, but don't have anything ready yet I'm
afraid. I can post a bpf-next patch to switch to using --btf_features
for v1.26 and later; might make Daniel's job a bit easier when adding
the kfunc stuff.
Alan
> - Arnaldo
>
prev parent reply other threads:[~2024-02-28 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 12:59 HEADS UP: pahole 1.26 to be released soon Arnaldo Carvalho de Melo
2024-02-27 13:00 ` Arnaldo Carvalho de Melo
2024-02-28 8:30 ` Jiri Olsa
2024-02-28 12:34 ` Arnaldo Carvalho de Melo
2024-02-28 13:54 ` Alan Maguire [this message]
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=39f96bb5-5285-418f-a2b3-0142ffbea23a@oracle.com \
--to=alan.maguire@oracle.com \
--cc=acme@kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=eddyz87@gmail.com \
--cc=olsajiri@gmail.com \
--cc=vmalik@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).