Regression failures on AARCH64

[pgowda-cve]

Hi,

I have built the image for ARM64 using Yocto sources and ran the regressions for bcc.
However, there are many test failures as shown below:-
I understand that something is missing from my side that's resulting in these failures

TOTAL: 61
PASS: 37
FAIL: 24 ( cc resolve symbol name in external zipped library; cc resolve symbol name via symfs; cc resolve symbol name via buildid; cc resolve symbol name via gnu_debuglink; cc resolve symbol name via mini debug info; cc resolve symbol addresses for a given PID; cc test bpf stack table; cc test bpf stack_id table; cc test hash of maps; cc test hash of maps using custom key; cc test array of maps; cc test read perf event; cc test usdt argument parsing; cc test finding a probe in our own process; cc test fine a probe in our own binary with C++ API; cc test fine probes in our own binary with C++ API; cc test fine a probe in our Process with C++ API; cc test find a probe in our process' shared libs with c++ API; cc test usdt partial init w/ fail init_usdt; cc Test uprobe refcnt semaphore activation; cc finds entries in a zip archive by name; cc finds entries in a zip archive by offset; cc open zip archive and finds an entry; cmake error, couldn't start python tests

My Kernel configurations
CONFIG_BPF=y
CONFIG_BPF_SYSCALL=y
CONFIG_NET_CLS_BPF=m
CONFIG_NET_ACT_BPF=m
CONFIG_BPF_JIT=y
CONFIG_HAVE_BPF_JIT=y
CONFIG_HAVE_EBPF_JIT=y
CONFIG_BPF_EVENTS=y
CONFIG_IKHEADERS=y

I investigated some of the errors and found a common error in many tests.
cannot attach kprobe, probe entry may not exist
However, I have the arm64 mentioned in syscall prefixes that should have fixed the error.
syscall_prefixes = [
b"sys",
b"_x64_sys",
b"_x32_compat_sys",
b"_ia32_compat_sys",
b"_arm64_sys",
b"_s390x_sys",
b"_s390_sys",
]

Can anyone please let me know if anything is amiss that's triggering these test failures?

Thanks,

[pgowda-cve]

Added the configurations for kprobe
CONFIG_KPROBE_EVENTS=y
CONFIG_KPROBES=y
CONFIG_HAVE_KPROBES=y
CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y
CONFIG_KPROBES_ON_FTRACE=y

But the issue still persists