[BUG] - Multi-core scheduling encounters data races

[bSchnepp]

Issue Checklist

• A related or similar issue is not already marked as open
• The steps to reproduce have been tested, and do produce the issue described
• If relevant, graphical issues have a screenshot presented as well. Text-only issues have the text and it's correct version listed within a Markdown code block section
• The most recent commit on the master branch the bug is present in, with it's commit hash, is listed in this report

=====================================================
Bug Description
A side-effect of switching processes seems to encounter some problems with memory accesses: either the TLB isn't completely purged as expected, or it is possible to enter a race condition where a page table switches but hasn't been updated for the current context.

To Reproduce
Please list the steps to produce the bug below:

1. Re-enable multi-core scheduling
2. Attempt to run the OS
3. A crash involving page table entries quickly occurs

Screenshots
If relevant, please provide screenshots here.

Expected behavior
Memory must always be in a consistent state

Additional information
Any additional information should be placed here.

[bSchnepp]

Possibly related to #28

[bSchnepp]

This may be a good opportunity to just go out and implement MuQSS ourselves. It would be nice to prove some things about the algorithm along the way (a low priority process never creates priority inversion, and will eventually be run again.) At a high level, it's easier to understand than CFS, and should provide some nice latency bounds anyway.