From: David Smith <dsmith@redhat.com>
To: William Cohen <wcohen@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: Wed, 17 Aug 2016 18:04:00 -0000 [thread overview]
Message-ID: <06cf3384-f909-dce5-b223-c25eb3ee49a9@redhat.com> (raw)
In-Reply-To: <eb6bb817-64f7-0a50-5f20-7797fd84b822@redhat.com>
On 08/17/2016 09:36 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:
>
> http://people.redhat.com/wcohen/aarch64/20160817/
... stuff deleted ...
> There are also some differences in the syscalls used on aarch64 that
> cause some of the tests to fail.
I looked a bit at those syscall failures, and I'm not sure what is going
on. Note that the syscall/nd_syscall test cases pass completely on RHEL7
aarch64. I did see one easy fix - you were getting registration errors
for the sched_[gs]etaffinity syscalls. Commit 619425f makes them fully
optional.
I'd need access to that machine to debug the other syscall failures further.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
next prev parent reply other threads:[~2016-08-17 18:04 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 [this message]
2016-08-17 18:28 ` William Cohen
2016-08-18 15:07 ` David Smith
2016-08-18 15:16 ` William Cohen
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=06cf3384-f909-dce5-b223-c25eb3ee49a9@redhat.com \
--to=dsmith@redhat.com \
--cc=broonie@linaro.org \
--cc=dave.long@linaro.org \
--cc=fche@redhat.com \
--cc=jlinton@redhat.com \
--cc=panand@redhat.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@redhat.com \
/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).