linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stevenrwalter@gmail.com (Steven Walter)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM support for syscall tracing
Date: Tue, 29 Nov 2011 11:28:12 -0500	[thread overview]
Message-ID: <1322584095-30439-1-git-send-email-stevenrwalter@gmail.com> (raw)

I recently noticed that "perf test" fails tests #2 - #4 on ARM.  In
investigating that failure, I noticed that those tests rely on
FTRACE_SYSCALLS, which was not available on ARM.

It didn't look like too much work to enable HAVE_SYSCALL_TRACEPOINTS, so
that's what I did in the patches that follow.  This is a
request-for-comment because I don't entirely understand some of the
changes I made, so it's quite likely that some parts are either
out-and-out wrong, or at least can be done a better way.

That said, the tests in "perf test" pass except for #1 (kallsyms), and
strace still seems to report sensible values for system calls.

Comments?

             reply	other threads:[~2011-11-29 16:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-29 16:28 Steven Walter [this message]
2011-11-29 16:28 ` [PATCH 1/3] ARM: add support for the generic syscall.h interface Steven Walter
2011-11-29 16:28 ` [PATCH 2/3] ARM: add TRACEHOOK support Steven Walter
2011-11-29 17:04   ` Will Deacon
2011-11-29 17:51     ` Steven Walter
2011-11-29 16:28 ` [PATCH 3/3] ARM: support syscall tracing Steven Walter
2011-11-29 17:24   ` Will Deacon
2011-11-29 18:02     ` Steven Walter
2011-11-29 17:46   ` Russell King - ARM Linux
2011-11-29 18:12     ` Steven Walter
2011-11-29 21:55       ` Russell King - ARM Linux

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=1322584095-30439-1-git-send-email-stevenrwalter@gmail.com \
    --to=stevenrwalter@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).