Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

General Multicore Improvements #121

Merged
merged 3 commits into from
May 25, 2023
Merged

Conversation

Apave24
Copy link

@Apave24 Apave24 commented Nov 11, 2022

These commits make the following general improvements:

  • add a camkes function to allow a component to get the affinity that was set for it in the camkes config
  • add a build time error checking for the affinity and num_vcpus attributes to avoid needing to wait for runtime errors to occur
  • allow a components fault handler thread to always be on the same core as it's control thread when the affinity attribute is set

Copy link
Member

@axel-h axel-h left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks ok to me.

@Apave24
Copy link
Author

Apave24 commented Mar 8, 2023

Bumping this PR. I believe everything has been addressed.

@axel-h
Copy link
Member

axel-h commented Mar 10, 2023

@Apave24 could you rebase this, then we also get another CI run there to see if this passes.

chrisguikema and others added 3 commits March 10, 2023 06:44
The fault handler thread currently is set to the default core which can
cause a component's fault handler threads and control threads to be on
separate cores if the affinity attribute is set. This change sets the
fault handler thread and control thread to run on the same core.

Signed-off-by: Alex Pavey <[email protected]>
@axel-h
Copy link
Member

axel-h commented Mar 10, 2023

Seems this is breaking the build on optiplex9020

  vm1/camkes.c:43:2: error: #error "Invalid Affinity Value of 1"
     43 | #error "Invalid Affinity Value of 1"
        |  ^~~~~

@kent-mcleod
Copy link
Member

Seems this is breaking the build on optiplex9020

That example appears to have a broken configuration that the new change is catching.

@kent-mcleod kent-mcleod merged commit 73c90a4 into seL4:master May 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants