All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"Frank Ch. Eigler" <fche@redhat.com>,
	Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH] [RFC] tracehook: Hook in syscall tracing markers.
Date: Mon, 22 Sep 2008 21:20:39 -0400	[thread overview]
Message-ID: <20080923012039.GA24937@Krystal> (raw)
In-Reply-To: <20080922010408.F53D.KOSAKI.MOTOHIRO@jp.fujitsu.com>

* KOSAKI Motohiro (kosaki.motohiro@jp.fujitsu.com) wrote:
> Hi Paul,
> 
> > At kernel summit, the idea that syscall tracing was generally desirable
> > for tracing was mentioned several times, as was the argument that kernel
> > developers aren't placing markers in meaningful locations. This is a
> > simple patch to try and do that for the syscall case.
> > 
> > Presently LTTng attempts to litter these trace markers all over the
> > architecture code, primarily to get around the fact that there was no
> > generic way to get at this information before. Now that platforms are
> > starting to do their syscall entry/exit notifiers through tracehook and
> > we have the asm/syscall.h interface, all of this information can be
> > generically abstracted.
> > 
> > Signed-off-by: Paul Mundt <lethal@linux-sh.org>
> > 
> 
> I think marriage between tracehook and generic marker is very good idea. 
> at least, instruction pointer and return value are definitly useful.
> 
> but...
> Have you seen Mathieu's tracepoint patch?
> I recommend to use tracepoint insted use marker directly.
> 

Yep, tracepoints would be better suited for this. They can be found in
-tip or in -lttng trees.

Does tracehook have any infrastructure that would give us the system
calls parameters (with correct typing ?) :-) Or could they evolve into
this ?

Mathieu

> 
> > ---
> > 
> >  include/linux/tracehook.h |    7 +++++++
> >  1 file changed, 7 insertions(+)
> > 
> > diff --git a/include/linux/tracehook.h b/include/linux/tracehook.h
> > index 6186a78..481ff45 100644
> > --- a/include/linux/tracehook.h
> > +++ b/include/linux/tracehook.h
> > @@ -49,6 +49,9 @@
> >  #include <linux/sched.h>
> >  #include <linux/ptrace.h>
> >  #include <linux/security.h>
> > +#include <linux/marker.h>
> > +#include <asm/syscall.h>
> > +
> >  struct linux_binprm;
> >  
> >  /**
> > @@ -112,6 +115,8 @@ static inline __must_check int tracehook_report_syscall_entry(
> >  	struct pt_regs *regs)
> >  {
> >  	ptrace_report_syscall(regs);
> > +	trace_mark(kernel_arch_syscall_entry, "syscall_id %ld ip #p%ld",
> > +		   syscall_get_nr(NULL, regs), instruction_pointer(regs));
> >  	return 0;
> >  }
> >  
> > @@ -135,6 +140,8 @@ static inline __must_check int tracehook_report_syscall_entry(
> >  static inline void tracehook_report_syscall_exit(struct pt_regs *regs, int step)
> >  {
> >  	ptrace_report_syscall(regs);
> > +	trace_mark(kernel_arch_syscall_exit, "ret %ld",
> > +		   syscall_get_return_value(NULL, regs));
> >  }
> 
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

  reply	other threads:[~2008-09-23  1:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-21  2:16 [PATCH] [RFC] tracehook: Hook in syscall tracing markers Paul Mundt
2008-09-22  1:12 ` KOSAKI Motohiro
2008-09-23  1:20   ` Mathieu Desnoyers [this message]
2008-09-22  1:28 ` Frank Ch. Eigler
2008-09-23  1:22   ` Mathieu Desnoyers
2008-09-26 10:42 ` Roland McGrath

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=20080923012039.GA24937@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=fche@redhat.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@redhat.com \
    --cc=torvalds@linux-foundation.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.