6.18: Add patch to read AMD CPU/TSC frequency from MSR #121
+193
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I had submitted a similar patch upstream here, however I am not sure if this will cause any issues, and I was told "Not sure if that is worth it" by one of the maintainers. This current version of the patch was also submitted here.
If there are any issues, Linux should automatically switch over to the HPET without the user noticing (this can also be forced with
tsc=unstable). Alternatively, removingsetup_force_cpu_cap(X86_FEATURE_TSC_KNOWN_FREQ);will allow linux to use the MSR timing for early in the boot process and keep this ~30ms speedup, but recalibrate later in the boot process.I've also only applied this to the 6.18rcs, to limit the exposure of any issues.