[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080718130754.GB32051@basil.nowhere.org>
Date: Fri, 18 Jul 2008 15:07:54 +0200
From: Andi Kleen <andi@...stfloor.org>
To: "Frank Ch. Eigler" <fche@...hat.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Andi Kleen <andi@...stfloor.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
systemtap@...rceware.org, jbeulich@...ell.com
Subject: Re: [RFC] systemtap: begin the process of using proper kernel APIs (part1: use kprobe symbol_name/offset instead of address)
> For example, we're about to do unwinding/stack-traces of userspace
> programs. To what extent do you think the kernel unwinder (should one
> reappear in git) would welcome patches that provide zero benefit to
> the kernel, but only enable a peculiar (nonintrusive) sort of
> unwinding we would need for complex userspace stacks?
In theory if the tables are right you don't need any special
for the kernel dwarf2 unwinder. If the tables are not right
fix them.
I believe oprofile did this already in some cases (generating
user back traces from the kernel)
-Andi
--
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