From: Vincent Li <vincent.mc.li@gmail.com>
To: bpf <bpf@vger.kernel.org>
Subject: Re: can't get BTF: type .rodata.cst32: not found
Date: Tue, 25 Jan 2022 09:52:42 -0800 [thread overview]
Message-ID: <CAK3+h2ybqBVKoaL-2p8eu==4LxPY2kfLyMsyOuWEVbRf+S-GbA@mail.gmail.com> (raw)
In-Reply-To: <CAK3+h2wcDceeGyFVDU3n7kPm=zgp7r1q4WK0=abxBsj9pyFN-g@mail.gmail.com>
this is macro I suspected in my implementation that could cause issue with BTF
#define ENABLE_VTEP 1
#define VTEP_ENDPOINT (__u32[]){0xec48a90a, 0xee48a90a, 0x1f48a90a,
0x2048a90a, }
#define VTEP_MAC (__u64[]){0x562e984c3682, 0x582e984c3682,
0x5eaaed93fdf2, 0x5faaed93fdf2, }
#define VTEP_NUMS 4
On Tue, Jan 25, 2022 at 9:38 AM Vincent Li <vincent.mc.li@gmail.com> wrote:
>
> Hi
>
> While developing Cilium VTEP integration feature
> https://github.com/cilium/cilium/pull/17370, I found a strange issue
> that seems related to BTF and probably caused by my specific
> implementation, the issue is described in
> https://github.com/cilium/cilium/issues/18616, I don't know much about
> BTF and not sure if my implementation is seriously flawed or just some
> implementation bug or maybe not compatible with BTF. Strangely, the
> issue appears related to number of VTEPs I use, no problem with 1 or 2
> VTEP, 3, 4 VTEPs will have problem with BTF, any guidance from BTF
> experts are appreciated :-).
>
> Thanks
>
> Vincent
next prev parent reply other threads:[~2022-01-25 17:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 17:38 can't get BTF: type .rodata.cst32: not found Vincent Li
2022-01-25 17:52 ` Vincent Li [this message]
2022-01-25 20:32 ` Vincent Li
2022-01-28 1:50 ` Yonghong Song
2022-01-28 18:27 ` Vincent Li
2022-02-01 18:07 ` Vincent Li
2022-02-02 7:17 ` Yonghong Song
2022-02-02 13:47 ` Timo Beckers
2022-02-02 19:55 ` Andrii Nakryiko
2022-02-03 2:11 ` Yonghong Song
2022-02-04 11:11 ` Timo Beckers
2022-02-04 18:04 ` Yonghong Song
2022-02-04 19:39 ` Vincent Li
2022-02-04 21:22 ` Yonghong Song
2022-02-07 21:53 ` Andrii Nakryiko
2022-02-08 6:47 ` Yonghong Song
2022-02-08 18:28 ` Vincent Li
2022-02-08 18:48 ` Vincent Li
2022-02-09 19:34 ` Yonghong Song
2022-02-09 19:53 ` Vincent Li
2022-05-06 14:11 ` Timo Beckers
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='CAK3+h2ybqBVKoaL-2p8eu==4LxPY2kfLyMsyOuWEVbRf+S-GbA@mail.gmail.com' \
--to=vincent.mc.li@gmail.com \
--cc=bpf@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.