[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9cac90ff-1a43-8663-da2e-7191975b5e93@codeaurora.org>
Date: Thu, 6 Sep 2018 08:26:20 +0530
From: Neeraj Upadhyay <neeraju@...eaurora.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: josh@...htriplett.org, peterz@...radead.org, mingo@...nel.org,
jiangshanlai@...il.com, dzickus@...hat.com,
brendan.jackman@....com, malat@...ian.org,
linux-kernel@...r.kernel.org, sramana@...eaurora.org,
linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH] cpu/hotplug: Fix rollback during error-out in
takedown_cpu()
On 09/05/2018 06:47 PM, Thomas Gleixner wrote:
> On Wed, 5 Sep 2018, Neeraj Upadhyay wrote:
>> On 09/05/2018 05:53 PM, Thomas Gleixner wrote:
>>> And looking closer this is a general issue. Just that the TEARDOWN state
>>> makes it simple to observe. It's universaly broken, when the first teardown
>>> callback fails because, st->state is only decremented _AFTER_ the callback
>>> returns success, but undo_cpu_down() increments unconditionally.
>>>
>> As per my understanding, there are 2 problems here; one is fixed with your
>> patch, and other is cpuhp_reset_state() is used during rollback from non-AP to
>> AP state, which seem to result in 2 increments of st->state (one increment
>> done by cpuhp_reset_state() and another by cpu_thread_fun()) .
> And how did your hack fix that up magically? I'll have a look later today.
>
> Thanks,
>
> tglx
The hack fixes it by not calling cpuhp_reset_state() and doing rollback
state reset inline inĀ _cpu_down().
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a
member of the Code Aurora Forum, hosted by The Linux Foundation
Powered by blists - more mailing lists