[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230118084923.m3ztfn6v3hskpad6@vireshk-i7>
Date: Wed, 18 Jan 2023 14:19:23 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Vincent Wang <bhuwz@....com>
Cc: rafael@...nel.org, lukasz.luba@....com, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org,
Vincent Wang <vincentwang3@...ovo.com>
Subject: Re: [PATCH v2] cpufreq: Register with perf domain before
On 18-01-23, 12:47, Vincent Wang wrote:
> From: Vincent Wang <vincentwang3@...ovo.com>
>
> We found the following issue during kernel boot on android phone:
>
> [ 1.325272][ T1] cpu cpu0: EM: created perf domain
> [ 1.329317][ T1] cpu cpu4: EM: created perf domain
> [ 1.337597][ T76] pd_init: no EM found for CPU7
> [ 1.350849][ T1] cpu cpu7: EM: created perf domain
>
> pd init for cluster2 is executed in a kworker thread and
> is earlier than the perf domain creation for cluster2.
Can you please give detail of the exact code path, for mainline kernel
? I am not sure which kworker thread are you talking about here.
> pd_init() is called from the cpufreq notification of
> CPUFREQ_CREATE_POLICY in cpufreq_online(), which is earlier
> than that cpufreq_driver->register_em() is called.
--
viresh
Powered by blists - more mailing lists