public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Pratyush Anand <panand@redhat.com>
To: William Cohen <wcohen@redhat.com>,
	systemtap@sourceware.org,
	       "arm@lists.fedoraproject.org"
	<arm@lists.fedoraproject.org>
Subject: Re: arm64 uprobes support showing signs of life
Date: Wed, 07 Jan 2015 12:07:00 -0000	[thread overview]
Message-ID: <54AD218B.6020002@redhat.com> (raw)
In-Reply-To: <54AAB673.6040200@redhat.com>

Hi Will,


On Monday 05 January 2015 09:36 PM, William Cohen wrote:
> Hi All,
>
> Pratyush has been implementing uprobes support for aarch64 and has
> posted a set of patches
> (http://comments.gmane.org/gmane.linux.ports.arm.kernel/382237) for
> review.  The really new Linux kernels requires a patch to the
> systemtap runtime because the f_dentry macro has been removed.  With
> the patched systemtap I was able to run the systemtap testsuite and
> get some test results exercising the uprobes support:
>
> https://web.elastic.org/~dejazilla/viewsummary.php?summary=%3D%27%3C54A9E21C.2080504%40redhat.com%3E%27
>
> There looked to be a localized fixes for plt support to eliminate the
> unsupported systemtap.base/list.exp plt-* tests.
>
> A number of the tests appear to fail because of userspace arguments
> cannot be found for sdt probes.
>
> The uprobe patches still need some refinement.  On a number of
> systemtap "make installcheck" runs the kernel would get stuck spewing
> out:
>
>    Unexpected kernel single-step exception at EL1

There are at least two functions of arm64/uprobe implementation 
uprobe_breakpoint_handler and uprobe_single_step_handler, where a kprobe 
insertion might be causing above issue. Currently I have qualified these 
functions with __kprobe, so that one can not insert a kprobe there. With 
this you should not be able to see the above message.

However, I am still investigating if a kprobe insertion be allowed to 
these functions or any other function which is called directly from 
debug exception handler (do_debug_exception)

Update code is here:

https://github.com/pratyushanand/linux.git : ml_arm64_uprobe_devel_v2

~Pratyush

>
> However, things are looking better for user-space probing on arm64.
>
> -Will
>

  parent reply	other threads:[~2015-01-07 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-05 16:06 William Cohen
2015-01-05 16:12 ` [fedora-arm] " Peter Robinson
2015-01-07 12:07 ` Pratyush Anand [this message]
2015-01-07 13:10   ` William Cohen
2015-01-07 13:34     ` 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=54AD218B.6020002@redhat.com \
    --to=panand@redhat.com \
    --cc=arm@lists.fedoraproject.org \
    --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).