-
Notifications
You must be signed in to change notification settings - Fork 70
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
Conversation
eb4b6bc
to
d1d5512
Compare
There was a problem hiding this 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.
d1d5512
to
6c2c7cd
Compare
Bumping this PR. I believe everything has been addressed. |
@Apave24 could you rebase this, then we also get another CI run there to see if this passes. |
Signed-off-by: Alex Pavey <[email protected]>
Signed-off-by: Alex Pavey <[email protected]>
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]>
6c2c7cd
to
5cee643
Compare
Seems this is breaking the build on optiplex9020
|
That example appears to have a broken configuration that the new change is catching. |
These commits make the following general improvements: