public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: systemtap@sourceware.org
Cc: Dave Long <dave.long@linaro.org>, Pratyush Anand <panand@redhat.com>
Subject: Recent aarch64 kprobes and uprobes patch systemtap testing
Date: Thu, 10 Dec 2015 20:24:00 -0000	[thread overview]
Message-ID: <5669DF98.3030601@redhat.com> (raw)

Hi All,

Dave Long and Pratyush Anand have been working on kprobe and uprobe patches for aarch64.  I have built a local version the uprobe/upstream_arm64_devel branch of https://github.com/pratyushanand/linux which includes those patches in a linux-4.4.0-rc3 kernel.

The tests seemed to run fairly well and the results have been uploaded to dejazilla:

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

		=== systemtap Summary ===

# of expected passes		6096
# of unexpected failures	111
# of unexpected successes	2
# of expected failures		333
# of unknown successes		2
# of known failures		89
# of untested testcases		97
# of unsupported tests		27
runtest completed at Thu Dec 10 05:54:32 2015


There are still some areas needing for for aarch64 such as stack backtrace support.

The following failure looks suspect because the child process died:


spawn stap -g ./systemtap.examples/process/threadstacks.stp -Gsize=65536 -c /root/systemtap_write/systemtap/testsuite/pthread_stacks.x 1024 0 -d /root/systemtap_write/systemtap/testsuite/pthread_stacks.x

pthread_stacks.x: ./systemtap.base/pthread_stacks.c:67: main: Assertion `rc == 0' failed.

WARNING: Child process exited with signal 6 (Aborted)

pthread_stacks.[3567] overwrote __default_stacksize@0x3ffb3be4338 (8388608->65536)

WARNING: /root/systemtap_write/install/bin/staprun exited with status: 1

Pass 5: run failed.  [man error::pass5]

FAIL: pthread_stacks -Gsize (0 0)

The fslatency-nd and fsslower-nd tests need further investigation:

PASS: ./systemtap.examples/lwtools/fslatency-nd build
meta taglines 'test_installcheck: stap fslatency-nd.stp 1 1' tag 'test_installcheck' value 'stap fslatency-nd.stp 1 1'
attempting command stap fslatency-nd.stp 1 1
OUT ERROR: read fault [man error::fault] at 0x0000000000000034 (addr) near operator '@cast' at fslatency-nd.stp:66:15
Tracing FS sync reads and writes... Output every 1 secs.
WARNING: Number of errors: 1, skipped probes: 1
WARNING: /root/systemtap_write/install/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]
child process exited abnormally
RC 1
FAIL: ./systemtap.examples/lwtools/fslatency-nd run

PASS: ./systemtap.examples/lwtools/fsslower-nd build
meta taglines 'test_installcheck: stap fsslower-nd.stp -c "sleep 1"' tag 'test_installcheck' value 'stap fsslower-nd.stp -c "sleep 1"'
attempting command stap fsslower-nd.stp -c "sleep 1"
OUT ERROR: read fault [man error::fault] at 0x0000000000000034 (addr) near operator '@cast' at fsslower-nd.stp:68:15
Tracing FS sync reads and writes slower than 10 ms... Hit Ctrl-C to end.
TIME     PID    COMM             FUNC           SIZE     LAT(ms)
WARNING: Number of errors: 1, skipped probes: 1
WARNING: /root/systemtap_write/install/bin/staprun exited with status: 1
Pass 5: run failed.  [man error::pass5]
child process exited abnormally
RC 1
FAIL: ./systemtap.examples/lwtools/fsslower-nd run


Also a number of network tests failed like the following 


TEST PWD=/root/systemtap_write/systemtap/testsuite/systemtap.examples/network
meta taglines 'test_check: stap -g -p4 netfilter_drop.stp TCP 1' tag 'test_check' value 'stap -g -p4 netfilter_drop.stp TCP 1'
attempting command stap -g -p4 netfilter_drop.stp TCP 1
OUT /tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2731:1: error: initialization from incompatible pointer type [-Werror]
 .hook = enter_netfilter_probe_0,
 ^
/tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2731:1: error: (near initialization for 'netfilter_opts_0.hook') [-Werror]
/tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2732:1: error: unknown field 'owner' specified in initializer
 .owner = THIS_MODULE,
 ^
/tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2732:1: error: initialization from incompatible pointer type [-Werror]
/tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.c:2732:1: error: (near initialization for 'netfilter_opts_0.dev') [-Werror]
cc1: all warnings being treated as errors
make[4]: *** [/tmp/stapbIEqFl/stap_0c0db8521e3ea3b2d26dcde208a77baf_21082_src.o] Error 1
make[3]: *** [_module_/tmp/stapbIEqFl] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed.  [man error::pass4]
child process exited abnormally
RC 1
FAIL: ./systemtap.examples/network/netfilter_drop build

-Will

             reply	other threads:[~2015-12-10 20:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 20:24 William Cohen [this message]
2015-12-10 21:12 ` David Long
2015-12-11  4:19   ` Pratyush Anand
2015-12-11  4:43     ` David Long
2015-12-11 17:02   ` William Cohen
2015-12-16  5:22     ` Pratyush Anand
2015-12-16 13:14       ` William Cohen
2015-12-17  0:53         ` Pratyush Anand
2015-12-11 20:59   ` William Cohen
2015-12-16 11:55     ` Pratyush Anand
2015-12-16 13:10       ` William Cohen
2015-12-10 21:17 ` David Long
2015-12-11 17:23 ` David Smith

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5669DF98.3030601@redhat.com \
    --to=wcohen@redhat.com \
    --cc=dave.long@linaro.org \
    --cc=panand@redhat.com \
    --cc=systemtap@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).