[all-commits] [llvm/llvm-project] de7ee2: [bolt][tests] Skip tests that use perf when perf c...

[Tom Stellard via All-commits]

  Branch: refs/heads/release/19.x
  Home:   https://github.com/llvm/llvm-project
  Commit: de7ee2e3ae893d61c0fa1a601e84ed538ec85e70
      https://github.com/llvm/llvm-project/commit/de7ee2e3ae893d61c0fa1a601e84ed538ec85e70
  Author: Tom Stellard <tstellar at redhat.com>
  Date:   2024-09-24 (Tue, 24 Sep 2024)

  Changed paths:
    M bolt/test/perf2bolt/lit.local.cfg

  Log Message:
  -----------
  [bolt][tests] Skip tests that use perf when perf counters are unavailable (#107892)

On the GitHub Action runners, perf always fails with the error below ,
so we need to skip the perf tests on platforms like this that have
limited access to the perf counters.

```
Access to performance monitoring and observability operations is limited.
Consider adjusting /proc/sys/kernel/perf_event_paranoid setting to open
access to performance monitoring and observability operations for processes
without CAP_PERFMON, CAP_SYS_PTRACE or CAP_SYS_ADMIN Linux capability.
More information can be found at 'Perf events and tool security' document:
https://www.kernel.org/doc/html/latest/admin-guide/perf-security.html
perf_event_paranoid setting is 4:
  -1: Allow use of (almost) all events by all users
      Ignore mlock limit after perf_event_mlock_kb without CAP_IPC_LOCK
>= 0: Disallow raw and ftrace function tracepoint access
>= 1: Disallow CPU event access
>= 2: Disallow kernel profiling
To make the adjusted perf_event_paranoid setting permanent preserve it
in /etc/sysctl.conf (e.g. kernel.perf_event_paranoid = <setting>)
```

(cherry picked from commit 773353b20a49bfa0dab608d415c1b4734d037fce)



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications