Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #368: The hw.vm.power_ratio metric is not collected leading to hw.power{hw.type="vm"} = 0 #420

Merged
merged 3 commits into from
Sep 20, 2024

Conversation

SafaeAJ
Copy link
Contributor

@SafaeAJ SafaeAJ commented Sep 20, 2024

  • Updated MappingProcessor, MappingProcessorTest, expected.json, VmPowerAndEnergyEstimator and HwConstants.java.
  • Tested on Nassim's PC.

@SafaeAJ SafaeAJ linked an issue Sep 20, 2024 that may be closed by this pull request
@SafaeAJ SafaeAJ self-assigned this Sep 20, 2024
@NassimBtk NassimBtk merged commit 2b1b94b into main Sep 20, 2024
2 checks passed
@NassimBtk NassimBtk deleted the feature/issue-368-km-module-issues-with-the-vm-class branch September 20, 2024 12:23
@NassimBtk NassimBtk changed the title Issue #368: KM module: issues with the VM class Issue #368: The hw.vm.power_ratio metric is not collected leading to hw.power{hw.type="vm"} = 0 Sep 20, 2024
@NathalieLe NathalieLe added this to the v0.9.07 milestone Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The hw.power{hw.type="vm"} metric is always set to 0
3 participants