From: Christoph Hellwig <hch@infradead.org>
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 2/2] utrace: ptrace cooperation
Date: Sat, 30 Aug 2008 09:38:34 -0400 [thread overview]
Message-ID: <20080830133834.GA17566@infradead.org> (raw)
In-Reply-To: <20080826220237.66B3D154233@magilla.localdomain>
On Tue, Aug 26, 2008 at 03:02:37PM -0700, Roland McGrath wrote:
>
> This adds the CONFIG_UTRACE_PTRACE option under CONFIG_UTRACE.
> When set, parts of ptrace are replaced so it uses the utrace
> facilities for noticing events, stopping and resuming threads.
>
> This makes ptrace play nicely with other utrace-based things
> tracing the same threads. It also makes all ptrace uses rely on
> some of the utrace code working right, even when you are not
> using any other utrace-based things. So it's experimental and
> not real well proven yet. But it's recommended if you enable
> CONFIG_UTRACE and want to try new utrace things.
I don't like this patch in it's current form. Having two different ways
to do ptrace is a rather awkward thing and not very good for testing
coverage. This should not be an option but required. I'm not even sure
keeping a non-utrace version at all is a good idea. I'd rather set a
deadline for arch maintainers to convert everything to the generic
ptrace bits + regsets + tracehook and if they don't manage to do it by
then ptrace will be disabled for those who can't keep up. Of course
this will need an announcement on linux-arch first, but it's much better
than a never ending phase of APIs in migration.
next prev parent reply other threads:[~2008-08-30 13:38 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 [this message]
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
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=20080830133834.GA17566@infradead.org \
--to=hch@infradead.org \
--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
Powered by JetHome