[PATCH] rteval: Set measurement cpuset to partition=isolated for CPU isolation

John Kacur <[email protected]> Fri, 10 Jul 2026 12:14:32 -0400
Newsgroups org.kernel.vger.linux-rt-users
Message-ID <[email protected]>
Change the rteval_measurement cpuset from partition=member to
partition=isolated to provide kernel-enforced CPU isolation for
measurement workloads.

With partition=isolated, the kernel prevents tasks from being scheduled
on measurement CPUs unless explicitly placed there, eliminating
interference from system tasks and the load balancer. This is essential
for accurate latency measurements.

The existing error handling in write_cpu_exclusive() ensures graceful
fallback to partition=member if isolated partitions are not supported
by the kernel.

Assisted-by: Claude:claude-sonnet-4-5
Signed-off-by: John Kacur <[email protected]>
---
 rteval/cpusetmanager.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rteval/cpusetmanager.py b/rteval/cpusetmanager.py
index 2fe931cc4574..abf5760db28c 100644
--- a/rteval/cpusetmanager.py
+++ b/rteval/cpusetmanager.py
@@ -125,7 +125,7 @@ class CpusetManager:
         self.measurement_cpuset = Cpuset('rteval_measurement')
         self.measurement_cpuset.write_memnode(self.numa_nodes)
         self.measurement_cpuset.assign_cpus(collapse_cpulist(self.measurement_cpus))
-        self.measurement_cpuset.write_cpu_exclusive(False)  # partition=member
+        self.measurement_cpuset.write_cpu_exclusive(True)  # partition=isolated
 
         self.logger.log(Log.INFO, "Cpusets created successfully")
         return self
-- 
2.54.0