[Fuego] cyclictest patches

Daniel Sangorrin daniel.sangorrin at toshiba.co.jp
Tue Oct 31 08:31:52 UTC 2017


Hi Tim,

I have modified the cyclictest benchmark test.

- cyclictest: update source code tarball

The previous source code was too old and lacked some important
flags. I added a patch to build the test for toolchains based on
old kernels (maybe this should be upstream)

TODO: rt-tests contains other tests that are already in Fuego
and can share the same tarball.
TODO: cyclictest requires some disturbance running in
background.

- [PATCH 1/3] cyclictest: update build function

I have tested the build in x86_64 and an ARM yocto-based toolchain.

- [PATCH 2/3] cyclictest: modify specs

The original spec was hardwiring cyclictest to use 2 threads. Now
the default is using 1 thread per core (with affinity).

- [PATCH 3/3] cyclictest: modify parsing and test measures

This is the biggest change and shows a limitation on using
static definitions (reference.json). The problem is described
on the commit message, but basically it boils down to the 
fact that the amount of test measures may depend on the
hardware (e.g.: number of cores) or spec (e.g.: number of 
threads). We need a mechanism to specify arrays of measures
that share the same 'units' and criteria.

I also had problems understanding chart_config.json.
With the one I have committed I expected that ony "max_latency"
would show up on jenkins. However all of them are displayed.

Cheers,
Daniel






More information about the Fuego mailing list