[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1911192326120.6731@nanos.tec.linutronix.de>
Date: Tue, 19 Nov 2019 23:31:38 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Qais Yousef <qais.yousef@....com>
cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will@...nel.org>,
Steve Capper <steve.capper@....com>,
Richard Fontana <rfontana@...hat.com>,
James Morse <james.morse@....com>,
Mark Rutland <mark.rutland@....com>,
Josh Poimboeuf <jpoimboe@...hat.com>,
Ingo Molnar <mingo@...nel.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>,
Nicholas Piggin <npiggin@...il.com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Jiri Kosina <jkosina@...e.cz>,
Pavankumar Kondeti <pkondeti@...eaurora.org>,
Zhenzhong Duan <zhenzhong.duan@...cle.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 01/12] arm64: hibernate.c: create a new function to handle
cpu_up(sleep_cpu)
On Wed, 30 Oct 2019, Qais Yousef wrote:
>
> +int hibernation_bringup_sleep_cpu(unsigned int sleep_cpu)
That function name is horrible. Aside of that I really have to ask how you
end up hibernating on an offline CPU?
> +{
> + int ret;
> +
> + if (!cpu_online(sleep_cpu)) {
> + pr_info("Hibernated on a CPU that is offline! Bringing CPU up.\n");
> + ret = cpu_up(sleep_cpu);
> + if (ret) {
> + pr_err("Failed to bring hibernate-CPU up!\n");
> + return ret;
> + }
> + }
> +}
Thanks,
tglx
Powered by blists - more mailing lists