Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp1116223ybc; Tue, 19 Nov 2019 14:55:35 -0800 (PST) X-Google-Smtp-Source: APXvYqxJtvMLyU60lBW+vBaej3L9Hm1ANxsojLX7upMJ/wAO+SrK5VUXN3vwpOx9Ki1CdpHA2irs X-Received: by 2002:a17:907:2122:: with SMTP id qo2mr304506ejb.12.1574204135387; Tue, 19 Nov 2019 14:55:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574204135; cv=none; d=google.com; s=arc-20160816; b=I/inzn7rvgcwXGIiSNOf9yWxYVPfG93nM4UA5GeqjT21niI4cGa2+rUhNcU9G4ZfnY YxaxgAxjqDO0o7oSAt9n+R9IYd+58MWEMPgmhl0Cku3P0XbZza+3JwRADORp3JbhBOak k+Ohx49aanuv/UdqtcSb2Akl3/ppjxhxTCWubDOtb0iMMupa2nVcsglnGm7wVau78fYT 09U0nfAO2r4gNeUW3NnLi6ZTBlra5nkqbD6OrBjYs87+jmru1kgVfka8kdsxXjqztA1j tvLlAcZsZ1VYlBeD9wvgdeNuB6tmQTBdJXv7bd/f5Inf3H13HquiUm0IQE718UCP6HqD F20w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=eJPOfEQCsJb4mrGjcR0Xc9un+ghYzXZjDFM4vyGtMRw=; b=lsZl9DtAxE9EvTPJ3sZNM7mWrAZofDpCmEhPP7M9Ds6FIdNsebYjSCTrsjBxm8/AH/ XotQ5Kc70vtypyqjm4oJ2rbu1rOUxcaBwd17X6EBhQbT5w6yMPXTO4znOiJ7Y1AKnAsX w8Gu3fNkCudFltXOHFRt2+19oHwO+HgOzbY/suDUbhS2MBw4SyNSZaNwalnp51PPOSJ6 LPDqVv/V8WRtdXIwIMD0G1vqdzYekuV/2CkRNRsolvHlvXES0sehgB+K7vCWS43VboWu 3h0YZDe30GrppK9KylSykEDeFkCtcz9YArTx9oBwq5BLDq7Oe4e2nFsKT2ej3f037Ayt eJ/A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f2si16209801ejf.231.2019.11.19.14.55.11; Tue, 19 Nov 2019 14:55:35 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727450AbfKSWvG (ORCPT + 99 others); Tue, 19 Nov 2019 17:51:06 -0500 Received: from foss.arm.com ([217.140.110.172]:59232 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726025AbfKSWvG (ORCPT ); Tue, 19 Nov 2019 17:51:06 -0500 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 81E911FB; Tue, 19 Nov 2019 14:51:05 -0800 (PST) Received: from e107158-lin.cambridge.arm.com (e107158-lin.cambridge.arm.com [10.1.195.21]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 41E2B3F52E; Tue, 19 Nov 2019 14:51:03 -0800 (PST) Date: Tue, 19 Nov 2019 22:51:00 +0000 From: Qais Yousef To: Thomas Gleixner Cc: Greg Kroah-Hartman , Catalin Marinas , Will Deacon , Steve Capper , Richard Fontana , James Morse , Mark Rutland , Josh Poimboeuf , Ingo Molnar , "Peter Zijlstra (Intel)" , Nicholas Piggin , Daniel Lezcano , Jiri Kosina , Pavankumar Kondeti , Zhenzhong Duan , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 01/12] arm64: hibernate.c: create a new function to handle cpu_up(sleep_cpu) Message-ID: <20191119225100.gqiiiwoyt3yntdoj@e107158-lin.cambridge.arm.com> References: <20191030153837.18107-1-qais.yousef@arm.com> <20191030153837.18107-2-qais.yousef@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/19/19 23:31, Thomas Gleixner wrote: > 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? James Morse can probably explain better. But AFAIU we could sleep on any CPU, but on the next cold boot that CPU could become offline as a side effect of using maxcpus= for example. How about bringup_hibernate_cpu() as a name? I could add the above as an explanation of why we need this call too. It does seem to me that this is a generic problem that we might be able to handle generically, but I'm not sure how. Thanks -- Qais Yousef