From: Andrew Morton <akpm@linux-foundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Alexey Dobriyan <adobriyan@gmail.com>,
Andi Kleen <andi@firstfloor.org>,
Ananth Mavinakayanahalli <ananth@in.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
"Frank Ch. Eigler" <fche@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Roland McGrath <roland@redhat.com>,
linux-kernel@vger.kernel.org, utrace-devel@redhat.com
Subject: Re: [PATCH 0/7] utrace/ptrace
Date: Tue, 22 Dec 2009 13:58:09 -0800 [thread overview]
Message-ID: <20091222135809.1ab10869.akpm@linux-foundation.org> (raw)
In-Reply-To: <20091218011116.GA29534@redhat.com>
On Fri, 18 Dec 2009 02:11:16 +0100
Oleg Nesterov <oleg@redhat.com> wrote:
> Hello.
>
> This is the new iteration of Roland's utrace patch, this time
> with "rewrite-ptrace-via-utrace" + cleanups in utrace core.
>
So... should we merge this?
I'll confess that I've rather forgotten why we might want this.
> It allows for multiple separate tracing engines to work
> in parallel without interfering with each other. Higher-level tracing
> facilities can be implemented as loadable kernel modules using this layer.
That's a bit brief. Do you have a nicer sales brochure? What are
these "separate tracing engines" and what is their merge status and why
would we want any of them, for what purpose? etc.
IOW: give us a reason!
next prev parent reply other threads:[~2009-12-22 21:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 1:11 [PATCH 0/7] utrace/ptrace Oleg Nesterov
2009-12-22 21:58 ` Andrew Morton [this message]
2009-12-23 17:42 ` Oleg Nesterov
2009-12-23 19:33 ` Roland McGrath
2009-12-23 19:47 ` Andi Kleen
2009-12-23 19:55 ` Roland McGrath
[not found] <1319782550.2227981262142487066.JavaMail.root@zmail06.collab.prod.int.phx2.redhat.com>
2009-12-30 3:09 ` caiqian
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=20091222135809.1ab10869.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=adobriyan@gmail.com \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=fche@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
--cc=utrace-devel@redhat.com \
/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.