You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On x86-64, Misaka uses use of the TSC as the sole clock source. Bochs, no matter how it's configured, does not provide the consistent TSC we need for this to make sense - the TSC remains tied to actual instruction cycles, so the passage of time can vary wildly depending on workload. Further, the initial timing of the TSC to wall clock is nearly random.
Linux, however, supports multiple clock sources, so if one is determined to be inaccurate or unusable, things can fall back to another. We could take a similar approach and provide alternative clock sources that are more likely to provide consistent timing information under Bochs, while still keeping the TSC for more normal circumstances.
The text was updated successfully, but these errors were encountered:
On x86-64, Misaka uses use of the TSC as the sole clock source. Bochs, no matter how it's configured, does not provide the consistent TSC we need for this to make sense - the TSC remains tied to actual instruction cycles, so the passage of time can vary wildly depending on workload. Further, the initial timing of the TSC to wall clock is nearly random.
Linux, however, supports multiple clock sources, so if one is determined to be inaccurate or unusable, things can fall back to another. We could take a similar approach and provide alternative clock sources that are more likely to provide consistent timing information under Bochs, while still keeping the TSC for more normal circumstances.
The text was updated successfully, but these errors were encountered: