public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Paul Mundt <lethal@linux-sh.org>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Mathieu Desnoyers <compudj@krystal.dyndns.org>,
	Roland McGrath <roland@redhat.com>
Subject: Re: [PATCH] [RFC] tracehook: Hook in syscall tracing markers.
Date: Sun, 21 Sep 2008 21:28:41 -0400	[thread overview]
Message-ID: <20080922012841.GA6199@redhat.com> (raw)
In-Reply-To: <20080921021630.GA6443@linux-sh.org>

Hi -

> 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.[...]

One problem with this is that a separate mechanism would be needed to
activate these tracehook_report_* calls in the first place: the
management of the per-task TIF_SYSCALL_TRACE flag.  This is one of the
things the utrace API makes straightforward, in which case its own
native syscall reporting callbacks can be used directly.

- FChE

  parent reply	other threads:[~2008-09-22  1:30 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
2008-09-22  1:28 ` Frank Ch. Eigler [this message]
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=20080922012841.GA6199@redhat.com \
    --to=fche@redhat.com \
    --cc=compudj@krystal.dyndns.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox