[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <y0mbpx71oqp.fsf@ton.toronto.redhat.com>
Date: Sun, 26 Oct 2008 09:15:42 -0400
From: fche@...hat.com (Frank Ch. Eigler)
To: =?ISO-8859-1?Q?Fr=E9d=E9ric_Weisbecker?= <fweisbec@...il.com>
Cc: =?ISO-8859-1?Q?T=F6r=F6k_Edwin?=
<edwintorok@...il.com>, mingo@...e.hu, srostedt@...hat.com,
a.p.zijlstra@...llo.nl, sandmann@...mi.au.dk,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] Add support for userspace stacktraces in tracing/iter_ctrl
"=?ISO-8859-1?Q?Fr=E9d=E9ric_Weisbecker?=" <fweisbec@...il.com> writes:
> [...]
>> +/* Userspace stacktrace - based on kernel/trace/trace_sysprof.c */
>> +
>> +struct stack_frame {
>> + const void __user *next_fp;
>> + unsigned long return_address;
>> +};
> [...]
To what extent does this actually work, and on which architectures?
While the kernel appears willing to sacrifice some performance for
functionality by building with frame pointers at the drop of a tracing
hat, userspace is not like that.
- FChE
--
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