Completing and merging core scheduling

"There were some questions about how Chrome OS uses core scheduling. It seems that all "system tasks" are allowed to run together, outside of any core-scheduling group. Browser-based tasks (which are nearly all user tasks in Chrome OS) are each put into their own group, and thus run isolated. In other words, the untrusted tasks are specially marked by the system. Peter Zijlstra remarked that this means tasks default to the trusted state, which seems insecure; he suggested that the default be untrusted instead."

On a system like Chrome OS? On my single-user Linux system, pretty much any program could copy arbitrary data to random servers, including tax and bank data I've had stored on system. At that level, there's no point in panicking about core scheduling. Browser-based tasks are the only times I'm running programs that aren't implicitly trust. That's the only time where worrying about side-channel attacks is important to me.