From: Eduard Zingerman <eddyz87@gmail.com>
To: Tony Ambardar <tony.ambardar@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
alan.maguire@oracle.com, dwarves@vger.kernel.org,
bpf@vger.kernel.org, andrii@kernel.org, martin.lau@linux.dev,
songliubraving@meta.com
Subject: Re: FYI: CI regression on big-endian arch (s390) after recent pahole changes
Date: Thu, 29 Aug 2024 18:40:59 -0700 [thread overview]
Message-ID: <e524ae6265bb34ebd2f68fc5c246b9c43235c15b.camel@gmail.com> (raw)
In-Reply-To: <ZtEgG6XJGIGn0z35@kodidev-ubuntu>
On Thu, 2024-08-29 at 18:27 -0700, Tony Ambardar wrote:
> Thanks for looking at this. I ran into the CI failure while using s390x
> to test a series adding libbpf bi-endian support. Since I'm deep into
> endianness issues right now, I thought to try the fix you suggested just
> to make some progress but noticed the CI failure has disappeared.[0]
Hi Tony,
There is no fix yet, sorry :)
I think that something like below should do the trick:
--- a/tools/lib/bpf/btf.c
+++ b/tools/lib/bpf/btf.c
@@ -5394,6 +5394,7 @@ int btf__distill_base(const struct btf *src_btf, struct btf **new_base_btf,
new_base = btf__new_empty();
if (!new_base)
return libbpf_err(-ENOMEM);
+ btf__set_endianness(new_base, btf__endianness(src_btf));
dist.id_map = calloc(n, sizeof(*dist.id_map));
if (!dist.id_map) {
err = -ENOMEM;
as far as I understand btf__raw_data() should do all conversions after this.
But I have not tested it yet and would be AFK for a few hours.
> Did something get fixed already? I can't seem to find the change.
pahole version w/o support for distilled base was pinned on CI:
https://github.com/kernel-patches/vmtest/pull/285/commits/d3eff26fc978ca8fb3bce3f93421f7425aef0f55
Thanks,
Eduard
next prev parent reply other threads:[~2024-08-30 1:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 0:05 FYI: CI regression on big-endian arch (s390) after recent pahole changes Eduard Zingerman
2024-08-30 1:27 ` Tony Ambardar
2024-08-30 1:40 ` Eduard Zingerman [this message]
2024-08-30 6:57 ` Tony Ambardar
2024-08-30 9:13 ` Eduard Zingerman
2024-08-30 2:49 ` Song Liu
2024-08-30 9:21 ` Eduard Zingerman
2024-08-30 10:05 ` Alan Maguire
2024-08-30 10:07 ` Eduard Zingerman
2024-08-30 13:19 ` Arnaldo Carvalho de Melo
2024-08-30 15:56 ` Andrii Nakryiko
2024-08-30 20:49 ` Arnaldo Carvalho de Melo
2024-08-30 22:20 ` Andrii Nakryiko
2024-08-30 22:34 ` Alan Maguire
2024-08-30 23:30 ` Andrii Nakryiko
2024-09-02 13:06 ` Alan Maguire
2024-09-02 14:08 ` Arnaldo Carvalho de Melo
2024-09-02 14:59 ` Alan Maguire
2024-09-02 18:44 ` Arnaldo Carvalho de Melo
2024-08-30 22:22 ` 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=e524ae6265bb34ebd2f68fc5c246b9c43235c15b.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=acme@kernel.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=songliubraving@meta.com \
--cc=tony.ambardar@gmail.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