[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5499283B.7020002@amacapital.net>
Date: Tue, 23 Dec 2014 00:30:51 -0800
From: Andy Lutomirski <luto@...capital.net>
To: root <chenggang.qin@...il.com>, linux-kernel@...r.kernel.org
CC: Chenggang Qin <chenggang.qcg@...bao.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
David Ahern <dsahern@...il.com>,
Ingo Molnar <mingo@...hat.com>, Mike Galbraith <efault@....de>,
Namhyung Kim <namhyung@...il.com>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Wu Fengguang <fengguang.wu@...el.com>,
Yanmin Zhang <yanmin.zhang@...el.com>
Subject: Re: [PATCH] perf core: Use KSTK_ESP() instead of pt_regs->sp while
output user regs
On 12/22/2014 10:22 PM, root wrote:
> From: Chenggang Qin <chenggang.qcg@...bao.com>
>
> For x86_64, the exact value of user stack's esp should be got by KSTK_ESP(current).
> current->thread.usersp is copied from PDA while enter ring0.
> Now, we output the value of sp from pt_regs. But pt_regs->sp has changed before
> it was pushed into kernel stack.
>
> So, we cannot get the correct callchain while unwind some user stacks.
> For example, if the stack contains __lll_unlock_wake()/__lll_lock_wait(), the
> callchain will break some times with the latest version of libunwind.
> The root cause is the sp that is used by libunwind may be wrong.
>
> If we use KSTK_ESP(current), the correct callchain can be got everytime.
> Other architectures also have KSTK_ESP() macro.
>
> Signed-off-by: Chenggang Qin <chenggang.qcg@...bao.com>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Cc: Arjan van de Ven <arjan@...ux.intel.com>
> Cc: David Ahern <dsahern@...il.com>
> Cc: Ingo Molnar <mingo@...hat.com>
> Cc: Mike Galbraith <efault@....de>
> Cc: Namhyung Kim <namhyung@...il.com>
> Cc: Paul Mackerras <paulus@...ba.org>
> Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> Cc: Wu Fengguang <fengguang.wu@...el.com>
> Cc: Yanmin Zhang <yanmin.zhang@...el.com>
>
> ---
> arch/x86/kernel/perf_regs.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/x86/kernel/perf_regs.c b/arch/x86/kernel/perf_regs.c
> index e309cc5..5da8df8 100644
> --- a/arch/x86/kernel/perf_regs.c
> +++ b/arch/x86/kernel/perf_regs.c
> @@ -60,6 +60,9 @@ u64 perf_reg_value(struct pt_regs *regs, int idx)
> if (WARN_ON_ONCE(idx >= ARRAY_SIZE(pt_regs_offset)))
> return 0;
>
> + if (idx == PERF_REG_X86_SP)
> + return KSTK_ESP(current);
> +
This patch is probably fine, but KSTK_ESP seems to be bogus:
unsigned long KSTK_ESP(struct task_struct *task)
{
return (test_tsk_thread_flag(task, TIF_IA32)) ?
(task_pt_regs(task)->sp) : ((task)->thread.usersp);
}
I swear that every time I've looked at anything that references TIF_IA32
in the last two weeks, it's been wrong. This should be something like:
if (task_thread_info(task)->status & TS_COMPAT)
return task_pt_regs(task)->sp;
else if (task == current && task is in a syscall)
return current_user_stack_pointer();
else if (task is not running && task is in a syscall)
return task->thread.usersp;
else if (task is not in a syscall)
return task_pt_regs(task)->sp;
else
we're confused; give up.
What context are you using KSTK_ESP in?
--Andy
> return regs_get_register(regs, pt_regs_offset[idx]);
> }
>
>
--
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