[PATCH] rteval: Don't restrict measurement threads to inherited cpumask

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



This patch reverses be811d28a471cfcaf7960289e00960e7f5b18f03

This patch syncs rteval to 795433f50f20ef7598db5cfe991b5386e4080d41 in
rt-tests

If the user does not specify a cpumask, rteval will still run on the
cpus according to the cpumask inherited from the runtime environment.
However, if the user specifies a cpumask, then it will overwrite the
runtime environment where allowed.

This will allow the user to run measurement threads on isolated cpus.

Signed-off-by: John Kacur <jkacur@xxxxxxxxxx>
---
 rteval/modules/measurement/cyclictest.py | 12 +-----------
 1 file changed, 1 insertion(+), 11 deletions(-)

diff --git a/rteval/modules/measurement/cyclictest.py b/rteval/modules/measurement/cyclictest.py
index 5330d1466302..4ca310bf7490 100644
--- a/rteval/modules/measurement/cyclictest.py
+++ b/rteval/modules/measurement/cyclictest.py
@@ -217,19 +217,9 @@ class Cyclictest(rtevalModulePrototype):
         else:
             self.__cpus = online_cpus()
 
-        # Sort the list of cpus to align with the order reported by
-        # cyclictest
+        # Sort the list of cpus to align with the order reported by cyclictest
         self.__cpus.sort(key=int)
 
-        # Get the cpuset from the environment
-        cpuset = os.sched_getaffinity(0)
-
-        # Convert the elements to strings
-        cpuset = [str(c) for c in cpuset]
-
-        # Only include cpus that are in the cpuset
-        self.__cpus = [c for c in self.__cpus if c in cpuset]
-
         self.__numcores = len(self.__cpus)
 
         info = cpuinfo()
-- 
2.34.1




[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux