variorum
variorum copied to clipboard
LLNL
Vendor-neutral library for exposing power and performance features across diverse architectures
IBM and ARM rely on opening/closing files to obtain (and set) power. These are significantly slower than MSR interfaces on Intel and AMD. We need to document such overheads clearly...
This was brought up at the PowerStack meeting in November, but is a bit low on the priority list compared to the other issues.
Suggestions include adding a switch to choose either metrics-as-rows or metrics-as-columns, add an iteration count, add a timestamp, etc. Needs to be done cross-platform.
One problem we run into often is the lack of availability of a certain microarchitecture. To address this, we plan to create a library that can generate fake power data...
Currently you have GitLab CI as well as a GitHub Actions declarations. It would be better to factor out e.g., shell scripting incorporated in the related YAML files into dedicated...
Several architectures (AMD & Intel CPUs, ARM, IBM) use `open(2)`. When this fails, give the user some actionable information and exit immediately. Perhaps implement `fsops_open()` and `fsops_fopen()` calls that, on...
As appropriate, e.g., based on ISA, generation, component type. This could help organize the growing list of issues. You can delegate such tasks to a larger pool of people or...
Update msr subsystem to account for the updated/disambiguated error message in msr-safe. This should include accounting for msr-safe versioning.
Thinking about this from container perspective
