On 2/28/19 5:48 PM, Qais Yousef wrote:
On 02/28/19 17:04, Dietmar Eggemann wrote:
Hi Joel,
On 2/28/19 3:47 PM, Joel Fernandes wrote:
On Thu, Feb 28, 2019 at 01:53:43PM +0000, Qais Yousef wrote:
Hi Joel
On 02/27/19 14:37, Joel Fernandes (Google) wrote:
[...]
The reason for me to stay on v4.20 is that with v5.0-rc8 I don't have ebpf
'raw tracepoint' support any more on my arm64 board. But this issue is not
related to your patch though.
And this is caused by a38d1107f937 (bpf: support raw tracepoints in modules)
which renamed bpf_find_raw_tracepoint() which bcc-tools relies on to detect if
raw tracepoints are supported..
https://github.com/iovisor/bcc/blob/master/src/python/bcc/__init__.py#L860
Speaking of fragile depedencies :-)
I guess the check can be extended to check for both symbols - but it'll stay
fragile. Not sure if they can do better.
I filed a bug
https://github.com/iovisor/bcc/issues/2240
This did the trick for me on v5.0-rc8. Thanks, Qais!
