Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1250980 > unrolled thread

Re: [PATCH v3] arm64: Synchronise dump_backtrace() with perf callchain

Started byCatalin Marinas <catalin.marinas@arm.com>
First post2015-10-19 20:10 +0200
Last post2015-10-19 20:10 +0200
Articles 1 — 1 participant

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH v3] arm64: Synchronise dump_backtrace() with perf  callchain Catalin Marinas <catalin.marinas@arm.com> - 2015-10-19 20:10 +0200

#1250980 — Re: [PATCH v3] arm64: Synchronise dump_backtrace() with perf callchain

FromCatalin Marinas <catalin.marinas@arm.com>
Date2015-10-19 20:10 +0200
SubjectRe: [PATCH v3] arm64: Synchronise dump_backtrace() with perf callchain
Message-ID<qln2G-3Iv-3@gated-at.bofh.it>
On Sat, Oct 17, 2015 at 02:28:11PM +0000, Jungseok Lee wrote:
> Note that this patch does not cover a case where MMU is disabled. The
> last stack frame of swapper, for example, has PC in a form of physical
> address. Unfortunately, a simple conversion using phys_to_virt() cannot
> cover all scenarios since PC is retrieved from LR - 4, not LR. It is
> a big tradeoff to change both head.S and unwind_frame() for only a few
> of symbols in *.S. Thus, this hunk does not take care of the case.

That's fine, I think we can cope with a physical address as the last
entry in the trace.

Patch queued for 4.4. Thanks.

-- 
Catalin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [standalone]


Back to top | Article view | linux.kernel


csiph-web