On Sun, Dec 11, 2016 at 5:27 PM, Ming Lei via iovisor-dev <iovisor-dev@lists.iovisor.org> wrote: > On Sun, Dec 11, 2016 at 9:21 AM, Chaiken, Alison via iovisor-dev > <iovisor-dev@lists.iovisor.org> wrote: >> Ming Lei <ming....@canonical.com> inquires: >> >> Bcc can be installed on ubuntu 16.04/arm64 successfully, but when >> I try to trace, the folllowing failure[1] is triggered. >> So is bcc not ready for arm64? Or something is wrong? > > Also for the prog building failure of 'LLVM ERROR: Inline asm', even though > it is workaround on x86, maybe one day some one changes kernel headers > under arch a bit and may cause the similar issue with arm64 too. > > So is there one generic solution for the issue? Is it possible to > preprocess the source file first and replace asm() with noop > or bpf_trace_printk(WARN)? Or other solutions?
not sure what the best approach here. we can try to ignore inline asm in the llvm during codegen, but since bpf backend was asked to emit such code, most likely it means that this asm is used somewhere so even if we ignore it, the generated code probably will be broken anyway and won't pass the verifier. Is there a way to reproduce it without bcc? so you can send me a pre-processed .c file or even better .ll file ? I don't have arm64 to reproduce it... Thanks _______________________________________________ iovisor-dev mailing list iovisor-dev@lists.iovisor.org https://lists.iovisor.org/mailman/listinfo/iovisor-dev
