Re: [PATCH bpf-next v3 05/11] bpf, arm64, powerpc: Add bpf_jit_bypass_spec_v1/v4()

On 01/05/25 1:05 pm, Luis Gerhorst wrote: JITs can set bpf_jit_bypass_spec_v1/v4() if they want the verifier to skip analysis/patching for the respective vulnerability. For v4, this will reduce the number of barriers the verifier inserts. For v1, it allows more programs to be accepted. The pr

Re: [PATCH v2 2/4] powerpc/perf: make isa207_pmu_format_group struct static

submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Madhavan-Srinivasan/powerpc-perf-make-isa207_pmu_format_group-struct-static/20250518-124244 base: https://git.

Re: [PATCH bpf-next v2 06/11] bpf, arm64, powerpc: Change nospec to include v1 barrier

On 21/04/25 2:47 pm, Luis Gerhorst wrote: This changes the semantics of BPF_NOSPEC (previously a v4-only barrier) to always emit a speculation barrier that works against both Spectre v1 AND v4. If mitigation is not needed on an architecture, the backend should set bpf_jit_bypass_spec_v4/v1().

[powerpc:merge] BUILD SUCCESS a9d887695c86d44fd23f612549cb8dc78a3a0f22

14.2.0 arc allmodconfiggcc-14.2.0 arc allnoconfiggcc-14.2.0 arc allyesconfiggcc-14.2.0 arc defconfiggcc-14.2.0 arc randconfig-001-20250518gcc-14.2.0 arc rand