[Bug translator/23866] dissonance between kernel tracepoint parametrization, lkm vs bpf

["wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=23866

William Cohen <wcohen at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #10 from William Cohen <wcohen at redhat dot com> ---
This should be addressed by the following commit:

commit fcdd71babea2435601e5e7f8b6b5faae4a663443
Author: William Cohen <wcohen@redhat.com>
Date:   Thu Jul 18 11:37:37 2019 -0400

    PR23866: Make the bpf backend use BPF raw tracepoints for kernel.trace("*")

    The BPF raw tracepoints provide arguments that better match the
    Systemtap lkm kernel tracepoint probes than regular BPF tracepoints.
    The BPF backend will use the BPF raw tracepoints unless the user
    specifies the old behavior with a --compatible=4.1 option on the
    commandline to address.

    The new BPF raw tracepoints and their argument are discovered in the
    same way as the old BPF tracepoints.  A number of small machine
    generated C files are generated with macros are compiled to query the
    available tracepoints in the kernel. Debug information describing the
    data structures passed into the BPF tracepoints is examined to
    determine the type and location of the tracepoint arguments.

    Each probe handler BPF code for BPF raw tracepoints is put into a
    raw_trace section as the method of registering the BPF raw tracepoints
    is different than the regular BPF tracepoints.

    The bpf tests have been revised to include the --compatible=4.1 option
    for the tests where it makes a difference.

-- 
You are receiving this mail because:
You are the assignee for the bug.