From: Christoph Hellwig <hch@lst.de>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
chris@zankel.net, cooloney@kernel.org, deller@gmx.de,
geert@linux-m68k.org, gerg@uclinux.org, hskinnemoen@atmel.com,
jdike@addtoit.com, jesper.nilsson@axis.com, kyle@mcmartin.ca,
linux@arm.linux.org.uk, ralf@linux-mips.org, rth@twiddle.net,
starvik@axis.com, takata@linux-m32r.org,
ysato@users.sourceforge.jp, zippel@linux-m68k.org,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: Fwd: arch/ && tracehook_report_syscall_xxx()
Date: Wed, 29 Apr 2009 21:44:12 +0200 [thread overview]
Message-ID: <20090429194412.GA3306@lst.de> (raw)
In-Reply-To: <20090429190852.GA14515@redhat.com>
On Wed, Apr 29, 2009 at 09:08:52PM +0200, Oleg Nesterov wrote:
> . Could you please convert your syscall trace code to use
> tracehook_report_syscall_entry/tracehook_report_syscall_exit ?
This is part of Roland's step by step cookbook for new-style ptrace,
so we should have most done. Is there anything that makes this more
urgent than the others steps for you?
next prev parent reply other threads:[~2009-04-29 19:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 18:04 arch/ && tracehook_report_syscall_xxx() Oleg Nesterov
2009-04-27 18:29 ` Roland McGrath
2009-04-27 18:32 ` Christoph Hellwig
2009-04-29 19:08 ` Fwd: " Oleg Nesterov
2009-04-29 19:17 ` Roland McGrath
2009-04-29 19:30 ` Ingo Molnar
2009-04-29 19:44 ` Christoph Hellwig [this message]
2009-04-29 19:53 ` Kyle McMartin
2009-04-27 18:43 ` Oleg Nesterov
2009-04-27 19:24 ` David Howells
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=20090429194412.GA3306@lst.de \
--to=hch@lst.de \
--cc=chris@zankel.net \
--cc=cooloney@kernel.org \
--cc=deller@gmx.de \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=hskinnemoen@atmel.com \
--cc=jdike@addtoit.com \
--cc=jesper.nilsson@axis.com \
--cc=kyle@mcmartin.ca \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=oleg@redhat.com \
--cc=ralf@linux-mips.org \
--cc=roland@redhat.com \
--cc=rth@twiddle.net \
--cc=starvik@axis.com \
--cc=takata@linux-m32r.org \
--cc=ysato@users.sourceforge.jp \
--cc=zippel@linux-m68k.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