Page Comparison

...

• Check if wperf-driver correctly loads and unloads its resources.

• Implement PMU (driver) resource acquisition lock and release.

  • wperf-driver should be able to release PMU resources if they are not used by user space application wperf.

• Make sure only one user space application can access wperf-driver’s PMU resources.

• Introduce “busy” state to wperf-driver.

  • All wperf user space instances should be able to tell if driver is currently “in use” by another wperf instance(s).

  • Note: this will be extended in Device Tree feature. Each driver will be able to communicate user space if resource is ready, acquired and ready to use (other “states” may be added later).

    • In DT architecture there will be N drivers, user space can acquire driver(s) leaving other driver for users' disposal. Currently if user space is for example counting core, other wperf instance can’t use DMC resource.

unCore PMU Driver Improvements

Current wperf-driver implementation is not auto detecting unCore PMU.

...

• Code review of current solution.

• Fix issue related to device being uninstalled after restart.

• Add bulletproof install / remove / driver status functionality to wperf-devgen.

  • Note: in the future we will introduce Device Tree feature.

    • This will expand on wperf-devgen tool which should be able to manage set of WindowsPerf drivers.

Driver Testing Framework

Current project lacks wperf-driver testing infrastructure. WindowsPerf DTF should introduce simple smoke test / canary test framework we can use to verify driver during development and CI/CD testing. Current

...