From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752954AbbJOOZH (ORCPT ); Thu, 15 Oct 2015 10:25:07 -0400 Received: from mail-pa0-f52.google.com ([209.85.220.52]:32785 "EHLO mail-pa0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751912AbbJOOZF (ORCPT ); Thu, 15 Oct 2015 10:25:05 -0400 Subject: Re: [PATCH v4 2/2] arm64: Expand the stack trace feature to support IRQ stack Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=windows-1252 From: Jungseok Lee In-Reply-To: <5617CE26.10604@arm.com> Date: Thu, 15 Oct 2015 23:24:57 +0900 Cc: takahiro.akashi@linaro.org, catalin.marinas@arm.com, will.deacon@arm.com, linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com, barami97@gmail.com, linux-kernel@vger.kernel.org Content-Transfer-Encoding: 7bit Message-Id: <179A25A2-C346-46C0-93D1-BABD4B6CB401@gmail.com> References: <1444231692-32722-1-git-send-email-jungseoklee85@gmail.com> <1444231692-32722-3-git-send-email-jungseoklee85@gmail.com> <5617CE26.10604@arm.com> To: James Morse X-Mailer: Apple Mail (2.1283) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Oct 9, 2015, at 11:24 PM, James Morse wrote: Hi James, [ ... ] > I think unwind_frame() needs to walk the irq stack too. [2] is an example > of perf tracing back to userspace, (and there are patches on the list to > do/fix this), so we need to walk back to the start of the first stack for > the perf accounting to be correct. I plan to do re-spin this series without [PATCH 2/2] since 1) Akashi's approach looks better than mine and 2) you have the perf patches for [2]. This would help us to move forward. Thoughts? [ ... ] > [0] sudo ./perf record -e mem:
:x -ag -- sleep 10 > [1] sudo ./perf report --call-graph --stdio > [2] http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html Best Regards Jungseok Lee From mboxrd@z Thu Jan 1 00:00:00 1970 From: jungseoklee85@gmail.com (Jungseok Lee) Date: Thu, 15 Oct 2015 23:24:57 +0900 Subject: [PATCH v4 2/2] arm64: Expand the stack trace feature to support IRQ stack In-Reply-To: <5617CE26.10604@arm.com> References: <1444231692-32722-1-git-send-email-jungseoklee85@gmail.com> <1444231692-32722-3-git-send-email-jungseoklee85@gmail.com> <5617CE26.10604@arm.com> Message-ID: <179A25A2-C346-46C0-93D1-BABD4B6CB401@gmail.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Oct 9, 2015, at 11:24 PM, James Morse wrote: Hi James, [ ... ] > I think unwind_frame() needs to walk the irq stack too. [2] is an example > of perf tracing back to userspace, (and there are patches on the list to > do/fix this), so we need to walk back to the start of the first stack for > the perf accounting to be correct. I plan to do re-spin this series without [PATCH 2/2] since 1) Akashi's approach looks better than mine and 2) you have the perf patches for [2]. This would help us to move forward. Thoughts? [ ... ] > [0] sudo ./perf record -e mem:
:x -ag -- sleep 10 > [1] sudo ./perf report --call-graph --stdio > [2] http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html Best Regards Jungseok Lee