Skip to content

rt-app: Don't validate cpuset in config#135

Open
cloehle wants to merge 1 commit intoscheduler-tools:masterfrom
cloehle:cloehle-master/remove-cpuset-config-validation
Open

rt-app: Don't validate cpuset in config#135
cloehle wants to merge 1 commit intoscheduler-tools:masterfrom
cloehle:cloehle-master/remove-cpuset-config-validation

Conversation

@cloehle
Copy link

@cloehle cloehle commented Mar 5, 2025

The existing validation of cpuset based on the maximum CPU having the index sysconf(_SC_NPROCESSORS_CONF) - 1 is flawed. CPUs can be hotplugged out or disabled by nosmt.
Hotplugging can even happen simultaneously to rt-app running, making the validation attempt futile.
Instead of attempting to validate the config just let it fail whenever sched_setaffinity() is called.

The existing validation of cpuset based on the maximum CPU having the
index sysconf(_SC_NPROCESSORS_CONF) - 1 is flawed. CPUs can be
hotplugged out or disabled by nosmt.
Hotplugging can even happen simultaneously to rt-app running, making
the validation attempt futile.
Instead of attempting to validate the config just let it fail whenever
sched_setaffinity() is called.

Signed-off-by: Christian Loehle <christian.loehle@arm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant