From: wade_farnsworth@mentor.com (Wade Farnsworth)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] ARM support for syscall tracing
Date: Fri, 23 Mar 2012 07:50:22 -0700 [thread overview]
Message-ID: <4F6C8DAE.9070209@mentor.com> (raw)
In-Reply-To: <4F54D0D4.7070905@mentor.com>
This is a rework of Steven Walter's syscall tracing patches first
posted here:
http://lists.infradead.org/pipermail/linux-arm-kernel/2011-November/074454.html
I've rebased the patches against the current mainline master branch, as well
as implemented several changes based on feedback from Will Deacon and
Russel King.
v2: - Tested on EABI and OABI.
- Removed an instance of the ?: operator in syscall_set_return_value()
- Moved #define of NR_syscalls to syscall.h
- Changed the test of NR_syscalls vs __NR_syscalls in entry-common.S
to .ifne
v3: - Added Will Deacon's Reviewed-by line. Code is identical to v2.
v4: - Updated comment and error string for the NR_syscalls test to
reflect that it's now testing for inequality.
Russell, now that this has been reviewed by Will and tested with both
ABIs, is this okay to submit to your patch tracker?
Wade Farnsworth (3):
ARM: add support for the generic syscall.h interface
ARM: add TRACEHOOK support
ARM: support syscall tracing
arch/arm/Kconfig | 2 +
arch/arm/include/asm/ptrace.h | 5 ++
arch/arm/include/asm/syscall.h | 97 ++++++++++++++++++++++++++++++++++++
arch/arm/include/asm/thread_info.h | 2 +
arch/arm/include/asm/unistd.h | 8 +++
arch/arm/kernel/entry-common.S | 18 ++++++-
arch/arm/kernel/ptrace.c | 34 +++++++------
arch/arm/kernel/signal.c | 2 +
8 files changed, 151 insertions(+), 17 deletions(-)
create mode 100644 arch/arm/include/asm/syscall.h
next prev parent reply other threads:[~2012-03-23 14:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 14:44 [PATCH 0/3] ARM support for syscall tracing Wade Farnsworth
2012-02-22 14:45 ` [PATCH 1/3] ARM: add support for the generic syscall.h interface Wade Farnsworth
2012-02-24 11:00 ` Will Deacon
2012-02-24 15:47 ` Wade Farnsworth
2012-02-22 14:46 ` [PATCH 2/3] ARM: add TRACEHOOK support Wade Farnsworth
2012-02-22 14:47 ` [PATCH 3/3] ARM: support syscall tracing Wade Farnsworth
2012-02-24 11:05 ` Will Deacon
2012-02-24 15:48 ` Wade Farnsworth
2012-02-29 14:34 ` [PATCH v2 0/3] ARM support for " Wade Farnsworth
2012-02-29 14:35 ` [PATCH v2 1/3] ARM: add support for the generic syscall.h interface Wade Farnsworth
2012-02-29 14:36 ` [PATCH v2 2/3] ARM: add TRACEHOOK support Wade Farnsworth
2012-02-29 14:36 ` [PATCH v2 3/3] ARM: support syscall tracing Wade Farnsworth
2012-02-29 18:29 ` [PATCH v2 0/3] ARM support for " Will Deacon
2012-03-05 14:42 ` [PATCH v3 " Wade Farnsworth
2012-03-05 14:43 ` [PATCH v3 1/3] ARM: add support for the generic syscall.h interface Wade Farnsworth
2012-03-05 14:43 ` [PATCH v3 2/3] ARM: add TRACEHOOK support Wade Farnsworth
2012-03-05 14:44 ` [PATCH v3 3/3] ARM: support syscall tracing Wade Farnsworth
2012-03-23 14:50 ` Wade Farnsworth [this message]
2012-03-23 14:51 ` [PATCH v4 1/3] ARM: add support for the generic syscall.h interface Wade Farnsworth
2012-03-23 14:52 ` [PATCH v4 2/3] ARM: add TRACEHOOK support Wade Farnsworth
2012-03-23 14:53 ` [PATCH v4 3/3] ARM: support syscall tracing Wade Farnsworth
2012-03-30 16:55 ` [PATCH v4 0/3] ARM support for " Will Deacon
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=4F6C8DAE.9070209@mentor.com \
--to=wade_farnsworth@mentor.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.