[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87my2bwtno.fsf@basil.nowhere.org>
Date: Tue, 24 Nov 2009 21:32:27 +0100
From: Andi Kleen <andi@...stfloor.org>
To: Oleg Nesterov <oleg@...hat.com>
Cc: Alexey Dobriyan <adobriyan@...il.com>,
Ananth Mavinakayanahalli <ananth@...ibm.com>,
Christoph Hellwig <hch@...radead.org>,
"Frank Ch. Eigler" <fche@...hat.com>, Ingo@...stfloor.org,
"Molnar <mingo"@firstfloor.org, utrace-devel@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [RFC,PATCH 14/14] utrace core
Oleg Nesterov <oleg@...hat.com> writes:
> From: Roland McGrath <roland@...hat.com>
>
> This adds the utrace facility, a new modular interface in the kernel
> for implementing user thread tracing and debugging. This fits on top
> of the tracehook_* layer, so the new code is well-isolated.
Could we just drop the tracehook layer if this finally merged
and call the low level functions directly?
It might have been reasonably early on when it was still out of tree,
but longer term when it's integrated having strange opaque hooks
like that just makes the coder harder to read and maintain.
-Andi
--
ak@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists