provider: add 'profile' provider

[ismhong]

The profile provider supports profiling by allowing the user to specify how many times it will fire pre-second. Values of 1-1000 are supported, and the profile provider supports two probe formats as it's original implementation commit 12b8ca2("profile provider support").

• profile:[N]hz: Profile on all CPUs N times per second
• profile:[C]:[N]hz: Profile on CPU C N times per second

Test this changes with 4 cores x86-64 PC as below.

$ sudo ./ply 'profile:2:100hz { @[cpu]=count(); } i:1s { print(@); }' 
@:
{  2 }: 100

@:
{  2 }: 200

@:
{  2 }: 300

$ sudo ./ply 'profile:100hz { @[cpu]=count(); } i:1s { print(@); }' 
@:
{  0 }: 100
{  1 }: 100
{  2 }: 100
{  3 }: 100

@:
{  0 }: 200
{  1 }: 200
{  2 }: 200
{  3 }: 200

@:
{  0 }: 300
{  1 }: 300
{  2 }: 300
{  3 }: 300

Change-Id: Ie669db20ed52947f5c75bf91c34f385a64029b19

[wkz]

This looks great! Sorry for the (extremely long) delay!

If you are still interested in getting this merged, would you mind:

• Rebasing on the latest master, so that we get regression testing on this branch
• Adding some new regression tests to test/rootfs/lib/ply/test.sh to cover the profile provider?

[ismhong]

Hi @wkz
I have rebased my PR with latest master, and add one regression test in test/rootfs/lib/ply/test.sh. Could you please help to review the changes? Thanks. :)

BTW, it seems there is a workflow changed notification Github raised due to rebase to latest master. I am not sure how to deal with it. Is there anything I done wrong while pushing changes to PR?

[wkz]

Thanks for hanging in there!

Please have a look at my suggestion for the test and see if you agree.