The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alexey Dobriyan <adobriyan@gmail.com>
To: Roland McGrath <roland@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] utrace
Date: Wed, 27 Aug 2008 22:50:54 +0400	[thread overview]
Message-ID: <20080827185054.GA30943@x200.localdomain> (raw)
In-Reply-To: <20080826223402.GB27724@x200.localdomain>

On Wed, Aug 27, 2008 at 02:34:02AM +0400, Alexey Dobriyan wrote:
> On Tue, Aug 26, 2008 at 03:01:02PM -0700, Roland McGrath wrote:
> > utrace is a new kernel-side API for kernel modules, intended to make it
> > tractable to work on novel ways to trace and debug user-mode tasks.
> 
> Finally! Familiar code! :^)
> 
> > A previous utrace prototype was in all Fedora kernels since Fedora Core 6.
> > Some substantial implementation and API details in the current code are
> > different from those past versions.
> 
> And some internal details still horrible and overdesigned just like at
> the very beginning.
> 
> > Please look freshly at these patches.
> 
> Well, all comments on tracehook patches were ignored.
> 
> > This code cannot be enabled without CONFIG_HAVE_ARCH_TRACEHOOK and the arch
> > details it indicates.  In Linus's tree as of v2.6.27-rc4, only powerpc and
> > sparc64 have that support.  The x86 support is available by merging in the
> > tip/x86/tracehook branch.  For working on other arch support, there are some
> > more details at http://sourceware.org/systemtap/wiki/utrace/arch/HowTo and
> > these are mentioned in the comments in arch/Kconfig too (in v2.6.27-rc4).
> > 
> > The first patch adds the utrace kernel API (if CONFIG_UTRACE=y is set).
> > There is no change at all without the config option, and with it there is
> > no effect on anything at all until a kernel module using the utrace API is
> > loaded.  There is detailed documentation on the API in DocBook form.
> > 
> > The second patch adds the CONFIG_UTRACE_PTRACE option.
> 
> If config option for ptrace is fine, please name it CONFIG_PTRACE.
> For one, there will be no second tracing infrastracture. For two, nobody
> but one man on the planet really cares how ptrace(2) is implemented.

Oh, I totally misread what this potion is about.

Of course, it shouldn't exist at all.


  parent reply	other threads:[~2008-08-27 18:49 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 22:01 [PATCH 0/2] utrace Roland McGrath
2008-08-26 22:01 ` [PATCH 1/2] utrace core Roland McGrath
2008-08-26 22:55   ` Alexey Dobriyan
2008-08-27 21:32     ` Alexey Dobriyan
2008-08-27 21:46       ` Alexey Dobriyan
2008-08-27 22:00         ` Alexey Dobriyan
2008-08-30 13:45     ` Christoph Hellwig
2008-09-03 12:11     ` Roland McGrath
2008-09-03 17:01       ` Alexey Dobriyan
2008-08-27 20:04   ` Alexey Dobriyan
2008-09-03 12:11     ` Roland McGrath
2008-09-03 18:44       ` Christoph Hellwig
2008-08-30 15:05   ` Alexey Dobriyan
2008-09-03 12:58   ` Petr Tesarik
2008-09-03 18:08     ` Roland McGrath
2008-09-03 18:46       ` Christoph Hellwig
2008-09-04  9:03         ` Petr Tesarik
2008-08-26 22:02 ` [PATCH 2/2] utrace: ptrace cooperation Roland McGrath
2008-08-30 13:38   ` Christoph Hellwig
2008-09-03 12:10     ` Roland McGrath
2008-09-03 18:41       ` Christoph Hellwig
2008-08-26 22:34 ` [PATCH 0/2] utrace Alexey Dobriyan
2008-08-26 22:39   ` Christoph Hellwig
2008-08-27  0:17   ` Frank Ch. Eigler
2008-08-27 13:54     ` Christoph Hellwig
2008-08-27 16:40       ` Ananth N Mavinakayanahalli
2008-08-30 13:40         ` Christoph Hellwig
2008-09-03 12:09           ` Roland McGrath
2008-09-03 18:37             ` Christoph Hellwig
2008-08-27 15:34     ` Alexey Dobriyan
2008-08-29 19:04       ` Frank Ch. Eigler
2008-08-30 13:43       ` Christoph Hellwig
2008-08-27 18:50   ` Alexey Dobriyan [this message]
2008-08-27  2:03 ` Peter Zijlstra
2008-10-06 20:47 ` Peter Zijlstra

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=20080827185054.GA30943@x200.localdomain \
    --to=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.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