From: fche@redhat.com (Frank Ch. Eigler)
To: Sandeepa Prabhu <sandeepa.prabhu@linaro.org>
Cc: systemtap@sourceware.org, William Cohen <wcohen@redhat.com>,
Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
Petr Machata <pmachata@redhat.com>,
Mark Wielaard <mjw@redhat.com>,
Deepak Saxena <dsaxena@linaro.org>,
Arnd Bergmann <arnd.bergmann@linaro.org>,
"sandeepa.prabhu@linux.com" <sandeepa.prabhu@linux.com>
Subject: Re: arm64 kprobes patches
Date: Wed, 26 Feb 2014 16:36:00 -0000 [thread overview]
Message-ID: <y0mzjldal1o.fsf@fche.csb> (raw)
In-Reply-To: <CA+b37P175OWKXcQ-4SYb+AudxOJMe3OC5csoZognNuX7MOaTyQ@mail.gmail.com> (Sandeepa Prabhu's message of "Wed, 26 Feb 2014 20:32:59 +0530")
Sandeepa Prabhu <sandeepa.prabhu@linaro.org> writes:
> Hi all,
> We have uploaded arm64 kprobes latest changes on linaro git which
> include some fixes for recursive kprobes. [...]
Great.
> Please let us know if you are interested in pulling this branch for
> systemtap test-suite verification, while we are trying to include
> systemtap test-suite on our linaro open-embedded platforms.
We will try soon.
> Also, please let us know if there are documentation on howto run full
> test-suite for systemtap and various criteria kprobes should meet?
The systemtap README includes these words:
[...]
To run a simple test.
# stap -v -e 'probe vfs.read {printf("read performed\n"); exit()}'
To run the full test suite from the build tree.
# make installcheck
[...]
The full installcheck suite exercises kprobes some, but not in a
stressful mode, like
probe kernel.function("*").* {}
That's partly because the x86 kernel has never been able to survive
such a test. It would be great if arm kprobes were robust enough.
- FChE
next prev parent reply other threads:[~2014-02-26 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 15:03 Sandeepa Prabhu
2014-02-26 16:36 ` Frank Ch. Eigler [this message]
2014-02-27 4:42 ` Sandeepa Prabhu
2014-02-27 11:48 ` Frank Ch. Eigler
2014-02-27 2:15 ` Masami Hiramatsu
2014-02-27 4:56 ` Sandeepa Prabhu
2014-02-27 6:04 ` Masami Hiramatsu
2014-02-27 6:19 ` Sandeepa Prabhu
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=y0mzjldal1o.fsf@fche.csb \
--to=fche@redhat.com \
--cc=arnd.bergmann@linaro.org \
--cc=dsaxena@linaro.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=mjw@redhat.com \
--cc=pmachata@redhat.com \
--cc=sandeepa.prabhu@linaro.org \
--cc=sandeepa.prabhu@linux.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).