diff options
author | Tejun Heo <tj@kernel.org> | 2025-04-09 22:06:00 +0300 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2025-04-09 22:06:00 +0300 |
commit | 54d2e717bc5f419b111915adfdec7ecc1ca8cf90 (patch) | |
tree | 2c1e6038ee7f8d7b906c94330634156db3128f15 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | cc39454c341e02b929e565f8a37cfe9b18c7a0a9 (diff) | |
download | linux-54d2e717bc5f419b111915adfdec7ecc1ca8cf90.tar.xz |
sched_ext: Remove scx_ops_cpu_preempt static_key
scx_ops_cpu_preempt is used to encode whether ops.cpu_acquire/release() are
implemented into a static_key. These tests aren't hot enough for static_key
usage to make any meaningful difference and are made to use a static_key
mostly because there was no reason not to. However, global static_keys can't
work with the planned hierarchical multiple scheduler support. Remove the
static_key and instead use an internal ops flag SCX_OPS_HAS_CPU_PREEMPT to
record and test whether ops.cpu_acquire/release() are implemented.
In repeated hackbench runs before and after static_keys removal on an AMD
Ryzen 3900X, I couldn't tell any measurable performance difference.
Signed-off-by: Tejun Heo <tj@kernel.org>
Acked-by: Changwoo Min <changwoo@igalia.com>
Acked-by: Andrea Righi <arighi@nvidia.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions