[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZVxyCsENJQ_-KZBMHjVrYCHzFG2UdCAe=mt_5Ts8_RFw@mail.gmail.com>
Date: Mon, 18 Jul 2022 11:12:54 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Li Huafei <lihuafei1@...wei.com>
Cc: linux@...linux.org.uk, rmk+kernel@...linux.org.uk, ardb@...nel.org,
will@...nel.org, mark.rutland@....com, broonie@...nel.org,
peterz@...radead.org, mingo@...hat.com, acme@...nel.org,
alexander.shishkin@...ux.intel.com, jolsa@...nel.org,
namhyung@...nel.org, arnd@...db.de, rostedt@...dmis.org,
nick.hawkins@....com, john@...ozen.org, mhiramat@...nel.org,
ast@...nel.org, linyujun809@...wei.com, ndesaulniers@...gle.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH 5/5] ARM: stacktrace: Convert stacktrace to generic ARCH_STACKWALK
On Tue, Jul 12, 2022 at 4:19 AM Li Huafei <lihuafei1@...wei.com> wrote:
> This patch converts ARM stacktrace to the generic ARCH_STACKWALK
> implemented by commit 214d8ca6ee85 ("stacktrace: Provide common
> infrastructure").
>
> Signed-off-by: Li Huafei <lihuafei1@...wei.com>
Looks good to me:
Reviewed-by: Linus Walleij <linus.walleij@...aro.org>
What I want to know is if this commit will avoid the problem mentioned
in review of commit 3? I.e. the generic stackwalk code will make sure we are
not running the task on another CPU, so that is why we could remove
that check?
Yours,
Linus Walleij
Powered by blists - more mailing lists