arm64 kprobes/systemtap support progress

[William Cohen]

On 11/21/2014 01:21 AM, David Long wrote:
> On 11/20/14 22:49, William Cohen wrote:
>> On 11/20/2014 05:56 PM, David Smith wrote:
>>> On 11/20/2014 10:14 AM, William Cohen wrote:
>>>> I did a quick look over of the current results and categorized most of
>>>> them below.
>>>
>>> ... stuff deleted ...
>>>
>>>> Uprobes support not available:
>>>>
>>>> FAIL: bad-code
>>>
>>> The above doesn't need uprobes, but it does to a user backtrace. (Or
>>> does a user backtrace require uprobes?)
>>
>> Hi David,
>>
>> For the bad-code it doesn't seem to use the uproces, but it gave message about user-space process-tracking facilities not being available:
>>
>> Running ./systemtap.base/bad-code.exp ...
>> Executing on host: gcc ./systemtap.base/bad-code.c  -g  -lm   -o bad-code    (timeout = 300)
>> spawn -ignore SIGHUP gcc ./systemtap.base/bad-code.c -g -lm -o bad-code
>>
>> PASS: bad-code.c compile
>> Running: stap ./systemtap.base/bad-code.stp -w -d ./bad-code -c ./bad-code
>> spawn stap ./systemtap.base/bad-code.stp -w -d ./bad-code -c ./bad-code
>>
>> user-space process-tracking facilities not available [man error::process-tracking]
>>
>> Pass 4: compilation failed.  [man error::pass4]
>>
>> Executing: kill -INT -4863
>> main: 0, func: 0, libc: 0
>> FAIL: bad-code
>>
>> Thanks for adding the fixes for the ones below.  I also added some fixes to address the syscall remappings for the syscall tests.  It looks like the failures might be less than 100 now.
>>
>> -Will
> 
> This is pretty good news.  Thanks for putting in so much effort.
> 
> -dl
> 
> 

Hi Dave and David,

The test results are now down to 83 failures:

https://web.elastic.org/~dejazilla/viewsummary.php?summary=%3D%27%3C546F297B.7010900%40redhat.com%3E%27

-Will