Idle function do not take care of Synchronizing the multi core states during S2I and S2R. #59285
Unanswered
SumitJain3083
asked this question in
Ideas
Replies: 1 comment
-
The policy made its decision per core based on the time of the next scheduled event. Much likely the policy will select the same state if these cores get idle closely. Note that states are per CPU, if one core is "special" you can have different states for it. Other possibility is to write your own policy that checks for other active cores before deciding which state to use. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In Multicore environment , if the policy manager decides that the system has to go to S2I or S2R then the idle framework will set S2I / S2R state for all the cores and once the pm_state_set is called on respective cores all the cores goes to suspend state.
or Is there a way to differentiate the last core and the other cores , so that the last core can be in different state then the other cores ?
Expected behavior
Expectation is last core shouldn't go to suspend mode in S2I / S2R.
Beta Was this translation helpful? Give feedback.
All reactions