From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2] arm64: skip register_cpufreq_notifier on ACPI-based systems
Date: Fri, 27 Jan 2017 11:31:04 +0000 [thread overview]
Message-ID: <20170127113103.GC27424@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <20170126181116.GT14167@arm.com>
On Thu, Jan 26, 2017 at 06:11:17PM +0000, Will Deacon wrote:
> On Thu, Jan 26, 2017 at 11:08:32AM -0700, Prashanth Prakash wrote:
> > On ACPI based systems where the topology is setup using the API
> > store_cpu_topology, at the moment we do not have necessary code
> > to parse cpu capacity and handle cpufreq notifier, thus
> > resulting in a kernel panic.
> >
> > Stack:
> > init_cpu_capacity_callback+0xb4/0x1c8
> > notifier_call_chain+0x5c/0xa0
> > __blocking_notifier_call_chain+0x58/0xa0
> > blocking_notifier_call_chain+0x3c/0x50
> > cpufreq_set_policy+0xe4/0x328
> > cpufreq_init_policy+0x80/0x100
> > cpufreq_online+0x418/0x710
> > cpufreq_add_dev+0x118/0x180
> > subsys_interface_register+0xa4/0xf8
> > cpufreq_register_driver+0x1c0/0x298
> > cppc_cpufreq_init+0xdc/0x1000 [cppc_cpufreq]
> > do_one_initcall+0x5c/0x168
> > do_init_module+0x64/0x1e4
> > load_module+0x130c/0x14d0
> > SyS_finit_module+0x108/0x120
> > el0_svc_naked+0x24/0x28
> >
> > Fixes: 7202bde8b7ae ("arm64: parse cpu capacity-dmips-mhz from DT")
> > Signed-off-by: Prashanth Prakash <pprakash@codeaurora.org>
> > ---
> > arch/arm64/kernel/topology.c | 8 +++++++-
> > 1 file changed, 7 insertions(+), 1 deletion(-)
>
> Acked-by: Will Deacon <will.deacon@arm.com>
>
> Catalin -- this resolves a panic, so please take it for 4.10
Applied. Thanks.
--
Catalin
prev parent reply other threads:[~2017-01-27 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 18:08 [PATCH V2] arm64: skip register_cpufreq_notifier on ACPI-based systems Prashanth Prakash
2017-01-26 18:11 ` Will Deacon
2017-01-27 11:31 ` Catalin Marinas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170127113103.GC27424@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).