From: William Cohen <wcohen@redhat.com>
To: David Smith <dsmith@redhat.com>, Pratyush Anand <panand@redhat.com>
Cc: David Long <dave.long@linaro.org>,
systemtap@sourceware.org, Mark Brown <broonie@linaro.org>,
Jeremy Linton <jlinton@redhat.com>,
"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: exercising current aarch64 kprobe support with systemtap
Date: Thu, 18 Aug 2016 15:16:00 -0000 [thread overview]
Message-ID: <666eed3a-b847-b2d5-fbb3-8bb860e30771@redhat.com> (raw)
In-Reply-To: <c2ba7d92-7ac3-28d2-255d-7beaad5540a7@redhat.com>
On 08/18/2016 11:06 AM, David Smith wrote:
...
> OK, here's the status of the [nd_]syscall test failures. There were 2
> failures caused by a test case being too specific when looking for
> syscall return value. There were fixed by commit 9c004b0:
>
> FAIL: 64-bit getgroups syscall
> FAIL: 64-bit setgroups syscall
>
> There are 4 failures caused by the atomic region kprobes registration bug:
>
> FAIL: 64-bit sched syscall
> FAIL: 64-bit sched_setaffinity syscall
> FAIL: 64-bit sched_setscheduler syscall
> FAIL: 64-bit set_tid_address syscall
>
> I verified all these failures by trying to use perf to put a probe on
> the same functions:
>
> ====
> # perf probe --add=sys_set_tid_address
> Failed to write event: Invalid argument
> Error: Failed to add events.
> ====
>
> I'm not seeing any issue with fork in the testsuite results, but perhaps
> I've missed something. What error are you referring to?
>
Sorry, I should have mentioned where I saw it. The fork issues weren't in the syscall tests. It was for procmod_wather.stp. Below is the part of systemtap.log that shows the problem:
meta taglines 'test_check: stap -p4 procmod_watcher.stp' tag 'test_check' value 'stap -p4 procmod_watcher.stp'
attempting command stap -p4 procmod_watcher.stp
OUT semantic error: while resolving probe point: identifier 'nd_syscall' at procmod_watcher.stp:47:7
source: probe nd_syscall.fork.return {
^
semantic error: no match
Pass 2: analysis failed. [man error::pass2]
child process exited abnormally
RC 1
FAIL: systemtap.examples/process/procmod_watcher build
meta taglines 'test_installcheck: stap procmod_watcher.stp -T 1' tag 'test_installcheck' value 'stap procmod_watcher.stp -T 1'
UNTESTED: systemtap.examples/process/procmod_watcher run
-Will
next prev parent reply other threads:[~2016-08-18 15:16 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 16:17 William Cohen
2016-06-09 19:52 ` William Cohen
2016-06-10 3:42 ` David Long
2016-06-10 5:49 ` David Long
2016-06-10 13:43 ` Pratyush Anand
2016-06-10 14:03 ` William Cohen
2016-06-10 14:37 ` David Long
2016-06-10 15:27 ` William Cohen
2016-06-10 14:20 ` David Long
2016-06-10 15:11 ` William Cohen
2016-06-10 17:07 ` Pratyush Anand
2016-07-12 14:33 ` William Cohen
2016-07-13 18:26 ` David Long
2016-07-13 18:47 ` Pratyush Anand
2016-07-13 19:45 ` William Cohen
2016-06-10 21:28 ` William Cohen
2016-06-10 21:37 ` William Cohen
2016-06-13 4:28 ` Pratyush Anand
2016-06-13 13:42 ` William Cohen
2016-06-22 20:24 ` William Cohen
2016-06-23 3:19 ` David Long
2016-06-23 13:42 ` William Cohen
2016-06-23 13:47 ` David Smith
2016-06-23 15:49 ` William Cohen
2016-06-23 18:26 ` David Long
2016-06-23 19:22 ` William Cohen
2016-06-27 2:57 ` David Long
2016-06-27 14:18 ` Pratyush Anand
2016-06-28 3:20 ` William Cohen
2016-07-04 12:46 ` Pratyush Anand
2016-07-07 19:05 ` David Long
2016-07-07 19:58 ` Frank Ch. Eigler
2016-08-03 13:13 ` Pratyush Anand
2016-08-03 14:51 ` William Cohen
2016-08-03 15:11 ` David Long
2016-08-03 17:40 ` William Cohen
2016-08-03 20:00 ` Lastest kprobes64 patch David Long
2016-08-03 20:01 ` Frank Ch. Eigler
2016-08-03 20:08 ` David Long
2016-08-04 5:03 ` Pratyush Anand
2016-08-04 13:07 ` David Long
2016-08-04 4:42 ` exercising current aarch64 kprobe support with systemtap Pratyush Anand
2016-08-04 13:57 ` William Cohen
2016-08-04 14:36 ` Pratyush Anand
2016-08-04 14:50 ` William Cohen
2016-08-04 20:51 ` William Cohen
2016-08-17 14:36 ` William Cohen
2016-08-17 18:04 ` David Smith
2016-08-17 18:28 ` William Cohen
2016-08-18 15:07 ` David Smith
2016-08-18 15:16 ` William Cohen [this message]
2016-08-18 15:39 ` David Smith
2016-08-18 14:55 ` Pratyush Anand
2016-06-13 16:11 ` William Cohen
2016-06-13 16:15 ` William Cohen
2016-06-14 4:27 ` Pratyush Anand
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=666eed3a-b847-b2d5-fbb3-8bb860e30771@redhat.com \
--to=wcohen@redhat.com \
--cc=broonie@linaro.org \
--cc=dave.long@linaro.org \
--cc=dsmith@redhat.com \
--cc=fche@redhat.com \
--cc=jlinton@redhat.com \
--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).