fix incorrect manipulation of cyclictest thread priorities

When running multiple measurement realtime threads (-t -p<N>),
cyclictest normally starts one thread with the specified priority N,
then decrements that priority for each subsequent thread. But,
using the histogram option (which rteval does) changes this logic
so that all measurement threads are equal priority. Change this in
cyclictest.py.

Signed-off-by: Clark Williams <williams@redhat.com>

1 files changed, 1 insertions, 1 deletions

diff --git a/rteval/cyclictest.py b/rteval/cyclictest.py
index 1c6f6f8..84d4024 100644
--- a/rteval/cyclictest.py
+++ b/rteval/cyclictest.py
@@ -164,7 +164,7 @@ class Cyclictest(Thread):
         for line in f:
             if line.startswith('processor'):
                 core = line.split()[-1]
-                self.data[core] = RunData(core, 'core', self.priority - int(core))
+                self.data[core] = RunData(core, 'core', self.priority)
                 numcores += 1
             if line.startswith('model name'):
                 desc = line.split(': ')[-1][:-1]