[Fuego] cyclictest patches

[Bird, Timothy]

> -----Original Message-----
> From: Daniel Sangorrin on Tuesday, October 31, 2017 9:32 AM
> I have modified the cyclictest benchmark test.

Thanks very much for this work.
 
> - 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.

The chart_config.json did not get quite all the way to completion
in terms of intended features.  (That's a nice way of saying that I
didn't finish it in time for the 1.2 release.)  Finishing it should be relatively
straightforward, but I really wanted to make the 1.2 release before
I went to ELCE.  I did, just barely, but didn't have time to announce it.
I'm still trying to get documentation ready for the 1.2 release, for 
the announcement.  I'll try to mention the limitations with chart_config.json
in the documentation I work on this week.  Fully finishing the new
charting (with flexible output control) and report generation is on
my 1.3 to-do list.  I'm hoping that 1.3 will have a much shorter development
cycle than 1.2 did.

I'll respond to individual patches with any issues or questions I have.
 -- Tim