Power Management Farm

  1. Linaro
  2. Engineering
  3. Core
  4. Arm-power-management
Director: Vincent Guittot
Lead Projects

Overview

Linaro's Power Management Working Group manages a board farm to boot kernels and run tests across various devices. Our main objectives include:

  • Monitor power consumption and performance trends of the Linux kernel and Android kernels and catch any performance and/or power regressions
  • Automate benchmarking of our team's development
  • Share hardware resources with the PMWG team

The PMWG board farm can be found at https://pmwg.validation.linaro.org.

Devices

Some devices in our board farm include:

  • Hikey6220
  • Hikey960
  • Pandaboard
  • Dragonboard 410c
  • Dragonboard 820c
  • Juno R2

Tools

We use these tools as a part of our testing process:

CI loop setup

Diagram

Our CI loop flow diagram can be found here.

Workloads, Device Configuration, and Agendas

We use the Linaro QA test definitions repository to run tests in our LAVA jobs. Specifically, we use the Workload Automation v3 test definitions for Android and Linux.

Please make sure that you have adb working in LAVA if you are running WA Android workloads, or SSH working in LAVA if you are running WA Linux workloads.

The WAv3 default device configuration files and agendas can be found from the Linaro QA wa-templates repository. PMWG specific agendas and config files can be found on our wa3-lava repository.

AEP setup

If you are planning to use arm energy probes to collect power measurements, you may need to perform one or more of these actions:

  • Check the probe is connected to the device. Some soldering may be needed.

  • On the host machine, install the libudev-dev package and add your username to the dialout group. Then run ls -l ../dev/ttyACM0.

  • Find the probe ID by running ls /dev/serial/by-id/ on the host machine. The output should look similar to this format: /dev/serial/by-id/usb-NXP_SEMICOND_ARM_Energy_Probe_S_NOXXXXXXXX-if00.

  • Update the LAVA device configuration file to include {% set static_info = [{'board_id': 'S_NOXXXXXXXX'}] %} where S_NOXXXXXXXX is the probe ID.

Data post processing

We are mainly using the sched-evaluation-full script in the LISA toolkit to post-process data.

Reporting

We use QA reports to display graphs and trends. QA reports uses the SQUAD tool to publish data pulled from LAVA.

LAVA job definition example

To get started, you can download this LAVA job definition and submit it on your LAVA instance. Please note that this example DOES NOT include the arm-probe, email notification, and post-processing sections that we use in our CI loops. You may need to change the device type and image links.

This example is created to get users running Workload Automation on Hikey Android in LAVA, and they can expand from there.

References

If you need general LAVA help (e.g. how to submit a job, how to install LAVA, tips for writing test definitions), please try one of the following suggestions:

  • Read the LAVA documentation. It is thoroughly written.

  • Email questions to the LAVA users mailing list at <lava-users AT lists DOT lavasoftware DOT org> so the LAVA team and other LAVA users can assist you, especially when everyone is in different timezones. Please attach job logs and job definition in your email if you have any. It is also very helpful to list the steps taken to reproduce your problem.

  • Visit the LAVA Software Community Project website.

  • Have a Linaro LDAP account and want to try running your first LAVA job? Visit here.

To learn how to use parameters or enable instruments in your agenda and how Workload Automation works in detail, please visit the WA document site.

If you experience issues with Workload Automation (e.g. can't run a workload, installation problems, reporting bugs), please create an issue at the Workload Automation github page.

If you need help setting up the LISA toolkit, please create an issue at the LISA toolkit github page.