You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Below is a snippet from a correspondence with Joe Mario regarding which sysctl fields from his area of expertise should be added to the kernel_report module:
as for my area (perf/bpf) I can tell you following parameters make some
sense to move and should be just simple read/write to do so:
kernel.perf_cpu_time_max_percent
kernel.perf_event_max_contexts_per_stack
kernel.perf_event_max_stack
kernel.perf_event_mlock_kb
kernel.perf_event_paranoid
kernel.bpf_stats_enabled
kernel.unprivileged_bpf_disabled
net.core.bpf_jit_enable
net.core.bpf_jit_harden
net.core.bpf_jit_kallsyms
net.core.bpf_jit_limit
These should be added to the list of acceptable sysctl fields and tested at some point in the future. Tied to PR #58.
The text was updated successfully, but these errors were encountered:
Below is a snippet from a correspondence with Joe Mario regarding which
sysctl
fields from his area of expertise should be added to the kernel_report module:These should be added to the list of acceptable
sysctl
fields and tested at some point in the future. Tied to PR #58.The text was updated successfully, but these errors were encountered: