tests: restrict realtime cpu
PATCH 1/1 tests: restrict realtime cpu
If there is no CPU restriction on the bootargs, smokey cpu_affinity test would be skipped reporting with "no kernel support".
tests/jobs/xenomai-beagle-bone-black.yml +2 -0
@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
tests/jobs/xenomai-hikey.yml +2 -0
@@ -70,3 +70,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
tests/jobs/xenomai-ipc227e.yml +2 -0
@@ -72,3 +72,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
tests/jobs/xenomai-minnow.yml +2 -0
@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
tests/jobs/xenomai-qemu-amd64.yml +2 -0
@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
tests/jobs/xenomai-qemu-arm64.yml +2 -0
@@ -93,3 +93,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
tests/jobs/xenomai-qemu-armhf.yml +2 -0
@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
tests/jobs/xenomai-x86-64-efi.yml +2 -0
@@ -72,3 +72,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
Signature · 1 line
2.17.1
Quoted 81 lines · Hongzhan Chen
If there is no CPU restriction on the bootargs, smokey
cpu_affinitytest would be skipped reporting with "no kernel support".Signed-off-by Hongzhan Chen <[email protected]>tests/jobs/xenomai-beagle-bone-black.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-hikey.yml +2
-0@@ -70,3 +70,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-ipc227e.yml +2
-0@@ -72,3 +72,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-minnow.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-amd64.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-arm64.yml +2
-0@@ -93,3 +93,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-armhf.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-x86-64-efi.yml +0
-0
tests/jobs/xenomai-x86-64-efi.yml actions: · line 76
Quoted 5 lines
tests/jobs/xenomai-x86-64-efi.yml +2
-0@@ -72,3 +72,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1
Let's not make all targets single-core regarding real-time. Rather, exclude one single-core from the real-time domain.
Jan
Signature · 2 lines
Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
Quoted 89 lines
-----Original Message-----
From: Jan Kiszka <[email protected]>
Sent: Wednesday, June 23, 2021 2:18 PM
To: Chen, Hongzhan <[email protected]>; [email protected]
Subject: Re: [xenomai-images PATCH] tests: restrict realtime cpuQuoted 81 lines · Hongzhan Chen
If there is no CPU restriction on the bootargs, smokey
cpu_affinitytest would be skipped reporting with "no kernel support".Signed-off-by Hongzhan Chen <[email protected]>tests/jobs/xenomai-beagle-bone-black.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-hikey.yml +2
-0@@ -70,3 +70,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-ipc227e.yml +2
-0@@ -72,3 +72,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-minnow.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-amd64.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-arm64.yml +2
-0@@ -93,3 +93,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-armhf.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-x86-64-efi.yml +0
-0@@ -72,3 +72,5 @@ actions: from: inline
Quoted 8 lines
tests/jobs/xenomai-x86-64-efi.yml actions: · line 76
Quoted 5 lines
tests/jobs/xenomai-x86-64-efi.yml +2
-0path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1Let's not make all targets single-core regarding real-time. Rather, exclude one single-core from the real-time domain.
If we pass invalid supported_cpus value, cpu-affinity test would return EINVAL error. That means we cannot set uniform value for different boards because different boards have different cpu configuration if we want to exclude one signal-core from real-time domain via xenomai.supported_cpus. In addition , I do not know the exact hardware cpu configuration for different target boards behind each lava test job.
Regards
Hongzhan Chen
Quoted 6 lines
Jan
Signature · 2 lines
Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
Quoted 98 lines · Hongzhan
Quoted 89 lines
-----Original Message-----
From: Jan Kiszka <[email protected]>
Sent: Wednesday, June 23, 2021 2:18 PM
To: Chen, Hongzhan <[email protected]>; [email protected]
Subject: Re: [xenomai-images PATCH] tests: restrict realtime cpuQuoted 81 lines · Hongzhan Chen
If there is no CPU restriction on the bootargs, smokey
cpu_affinitytest would be skipped reporting with "no kernel support".Signed-off-by Hongzhan Chen <[email protected]>tests/jobs/xenomai-beagle-bone-black.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-hikey.yml +2
-0@@ -70,3 +70,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-ipc227e.yml +2
-0@@ -72,3 +72,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-minnow.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-amd64.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-arm64.yml +2
-0@@ -93,3 +93,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-armhf.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-x86-64-efi.yml +0
-0@@ -72,3 +72,5 @@ actions: from: inlineQuoted 8 lines
tests/jobs/xenomai-x86-64-efi.yml actions: · line 76
Quoted 5 lines
tests/jobs/xenomai-x86-64-efi.yml +2
-0path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1Let's not make all targets single-core regarding real-time. Rather, exclude one single-core from the real-time domain.
Quoted 5 lines
If we pass invalid
supported_cpusvalue, cpu-affinity test would return EINVAL error. That means we cannot set uniform value for different boards because different boards have different cpu configuration if we want to exclude one signal-core from real-time domain via xenomai.supported_cpus. In addition , I do not know the exact hardware cpu configuration for different target boards behind each lava test job.
You can extract the information from the test logs, see e.g.
https://source.denx.de/Xenomai/xenomai-images/-/jobs/281065, "SMP: Total of 1 processors activated (996.14 BogoMIPS)."
Jan
Signature · 2 lines
Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
Quoted 113 lines
-----Original Message-----
From: Jan Kiszka <[email protected]>
Sent: Wednesday, June 23, 2021 5:15 PM
To: Chen, Hongzhan <[email protected]>; [email protected]
Subject: Re: [xenomai-images PATCH] tests: restrict realtime cpuQuoted 98 lines · Hongzhan
Quoted 89 lines
-----Original Message-----
From: Jan Kiszka <[email protected]>
Sent: Wednesday, June 23, 2021 2:18 PM
To: Chen, Hongzhan <[email protected]>; [email protected]
Subject: Re: [xenomai-images PATCH] tests: restrict realtime cpuQuoted 81 lines · Hongzhan Chen
If there is no CPU restriction on the bootargs, smokey
cpu_affinitytest would be skipped reporting with "no kernel support".Signed-off-by Hongzhan Chen <[email protected]>tests/jobs/xenomai-beagle-bone-black.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-hikey.yml +2
-0@@ -70,3 +70,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-ipc227e.yml +2
-0@@ -72,3 +72,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-minnow.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-amd64.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-arm64.yml +2
-0@@ -93,3 +93,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-armhf.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-x86-64-efi.yml +0
-0@@ -72,3 +72,5 @@ actions: from: inlineQuoted 8 lines
tests/jobs/xenomai-x86-64-efi.yml actions: · line 76
Quoted 5 lines
tests/jobs/xenomai-x86-64-efi.yml +2
-0path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1Let's not make all targets single-core regarding real-time. Rather, exclude one single-core from the real-time domain.
Quoted 5 lines
If we pass invalid
supported_cpusvalue, cpu-affinity test would return EINVAL error. That means we cannot set uniform value for different boards because different boards have different cpu configuration if we want to exclude one signal-core from real-time domain via xenomai.supported_cpus. In addition , I do not know the exact hardware cpu configuration for different target boards behind each lava test job.
Quoted 3 lines
You can extract the information from the test logs, see e.g.
https://source.denx.de/Xenomai/xenomai-images/-/jobs/281065, "SMP: Total of 1 processors activated (996.14 BogoMIPS)."
What about xenomai-ipc227e.yml and xenomai-minnow.yml? I cannot find any log for them and seems these two jobs never run. Do I need to touch them?
In addition, our patch does not work for single cpu system.
Regards
Hongzhan Chen
Quoted 6 lines
Jan
Signature · 2 lines
Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux
Quoted 113 lines · Hongzhan
Quoted 113 lines
-----Original Message-----
From: Jan Kiszka <[email protected]>
Sent: Wednesday, June 23, 2021 5:15 PM
To: Chen, Hongzhan <[email protected]>; [email protected]
Subject: Re: [xenomai-images PATCH] tests: restrict realtime cpuQuoted 103 lines · Hongzhan
Quoted 89 lines
-----Original Message-----
From: Jan Kiszka <[email protected]>
Sent: Wednesday, June 23, 2021 2:18 PM
To: Chen, Hongzhan <[email protected]>; [email protected]
Subject: Re: [xenomai-images PATCH] tests: restrict realtime cpuQuoted 81 lines · Hongzhan Chen
If there is no CPU restriction on the bootargs, smokey
cpu_affinitytest would be skipped reporting with "no kernel support".Signed-off-by Hongzhan Chen <[email protected]>tests/jobs/xenomai-beagle-bone-black.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-hikey.yml +2
-0@@ -70,3 +70,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-ipc227e.yml +2
-0@@ -72,3 +72,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-minnow.yml +2
-0@@ -71,3 +71,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-amd64.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-arm64.yml +2
-0@@ -93,3 +93,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-qemu-armhf.yml +2
-0@@ -87,3 +87,5 @@ actions: from: inline path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1tests/jobs/xenomai-x86-64-efi.yml +0
-0@@ -72,3 +72,5 @@ actions: from: inlineQuoted 8 lines
tests/jobs/xenomai-x86-64-efi.yml actions: · line 76
Quoted 5 lines
tests/jobs/xenomai-x86-64-efi.yml +2
-0path: inline/xenomai-test-suite.yaml name: xenomai-test-suite +context: + extra_kernel_args: xenomai.supported_cpus=1Let's not make all targets single-core regarding real-time. Rather, exclude one single-core from the real-time domain.
If we pass invalid
supported_cpusvalue, cpu-affinity test would return EINVAL error. That means we cannot set uniform value for different boards because different boards have different cpu configuration if we want to exclude one signal-core from real-time domain via xenomai.supported_cpus. In addition , I do not know the exact hardware cpu configuration for different target boards behind each lava test job.
Quoted 6 lines
Quoted 3 lines
You can extract the information from the test logs, see e.g.
https://source.denx.de/Xenomai/xenomai-images/-/jobs/281065, "SMP: Total of 1 processors activated (996.14 BogoMIPS)."What about xenomai-ipc227e.yml and xenomai-minnow.yml? I cannot find any log for them and seems these two jobs never run. Do I need to touch them?
Yeah, confusing: The 227e is the x86 target, eg.
https://source.denx.de/Xenomai/xenomai-images/-/jobs/281072. We don't have the minnow in the rack because it turned out to be too borken firmware-wise. Maybe time to drop that file.
Quoted 2 lines
In addition, our patch does not work for single cpu system.
Right, single-core targets (but that should only be the BBB in the rack) needs to be be skipped.
Jan
Signature · 2 lines
Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux