Re: exercising current aarch64 kprobe support with systemtap

[Pratyush Anand <panand@redhat.com>]

Hi Will,

On 17/08/2016:10:36:23 AM, William Cohen wrote:
> Hi,
> 
> I was able to locally build uptream_arm64-devel branch of  https://github.com/pratyushanand/linux.git with the configure from fedora rawhide and run the systemtap tests. Pratyush were there changes in patches between these versions?  The only other difference is that the machine above was a fedora 24 machine rather than a RHELSA, so there would be differences in the compiler and other tools. The results (systemtap.log and systemtap.sum) are at:

I had rebased it over 4.8-rc2. This would have been the only change.

~Pratyush

> 
> http://people.redhat.com/wcohen/aarch64/20160817/
> 
> I the results have been sent to dejazilla, but dejazilla appears to be having issues with displaying results (https://web.elastic.org/~dejazilla/viewsummary.php?summary=%3D%27%3Ccdc0ada3-26b8-295d-2d3b-d8a88da83e17%40redhat.com%3E%27)
> 
> The results look pretty respectable
> 
> 		=== systemtap Summary ===
> 
> # of expected passes		8809
> # of unexpected failures	69
> # of unexpected successes	1
> # of expected failures		339
> # of unknown successes		3
> # of known failures		95
> # of untested testcases		749
> # of unsupported tests		33
> 
> There are about a dozen failures due to the the search for atomic regions going beyond the beginning of the function which prevents probes on a number of functions like the following test:
> 
> spawn stap /root/systemtap_write/systemtap/testsuite/systemtap.base/bz1027459.stp
> WARNING: probe kernel.function("SyS_set_tid_address@kernel/fork.c:1234").call (address 0xfffffc00080cb528) registration error (rc -22)
> WARNING: probe kernel.function("SyS_sched_setaffinity@kernel/sched/core.c:4716").call (address 0xfffffc00081051b0) registration error (rc -22)
> WARNING: probe kernel.function("SyS_sched_get_priority_min@kernel/sched/core.c:5040").call (address 0xfffffc0008105688) registration error (rc -22)
> WARNING: probe kernel.function("SyS_sched_get_priority_max@kernel/sched/core.c:5013").call (address 0xfffffc0008105620) registration error (rc -22)
> 
> There are also some differences in the syscalls used on aarch64 that cause some of the tests to fail.
> 
> -Will