Repository navigation
kvm: prefer the base speed for AMD CPUs + a few refactorings - #14384
Open
winterhazel wants to merge 1 commit into
Open
winterhazel wants to merge 1 commit into
winterhazel wants to merge 1 commit into
Conversation
Member
Author
|
@blueorangutan package |
|
@winterhazel a [SL] Jenkins job has been kicked to build packages. It will be bundled with no SystemVM templates. I'll keep you posted as I make progress. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #14384 +/- ##
============================================
+ Coverage 20.05% 20.22% +0.17%
- Complexity 20656 20765 +109
============================================
Files 6427 6426 -1
Lines 584905 580203 -4702
Branches 71658 71036 -622
============================================
+ Hits 117278 117329 +51
+ Misses 454802 450165 -4637
+ Partials 12825 12709 -116
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 19515 |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This is a breaking change, so additional discussion may be required. It also contains the changes of #14383, so please review and merge the latter previously.
Many CPUs (notably AMD EPYC) do not advertise a frequency in the model name, so those hosts fell back to
CPU max MHz, which can include the turbo frequency. Since the host CPU speed is used to compute host capacity (cpus * speed) and the CPU quota of VMs with CPU cap enabled, using a turbo value is not correct because it is not a frequency the CPU can actually sustain.This PR inserts the CPU frequency sysfs files (
/sys/devices/system/cpu/cpu0/cpufreq/base_frequency, thenscaling_max_freq) before thelscpumaximum frequency fallback, so the resolution order becomes:lscpuModel namefield (x86) orCPU dynamic MHz(s390x)base_frequency, thenscaling_max_freq)lscpuCPU max MHzlscpuhost capabilitiesNodeInfo.mhzBehaviour for Intel hosts (whose model name carries
@ x.xxGHz) is unchanged.Additionally, I made a few refactorings throughout the
KVMHostInfofile.Types of changes
Feature/Enhancement Scale or Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
Tests are still pending.