Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp1862508ybc; Wed, 20 Nov 2019 05:22:44 -0800 (PST) X-Google-Smtp-Source: APXvYqy5pRqb9WorVrNvMkm9FyLnsTAy+hSPxS0CABkhsU8uTYPECVWcNXQVMT9QKHbzIR3hlMf2 X-Received: by 2002:a1c:113:: with SMTP id 19mr3379022wmb.42.1574256164553; Wed, 20 Nov 2019 05:22:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1574256164; cv=none; d=google.com; s=arc-20160816; b=SB+i6VUS11rx5rufahlos8DJfT1C3rlbSqmLNyorH+siACI64Hj9Wgcp7rvS2CCTHt cFNaSVU9s07D8BIe3/G/K1wQO+pX7xyJE1wsM84+unBU6J9l5jElLyjDHlYEyVaoWmnG 8adHiahoinLWpIZ2FX85NiuegS/vEgWOyGSGsEM85SMQJmPSSQ8Pt22IdFK6VzASBbtK IcrLYxHKrIZKeGa8pSzCYcHZZXLuqmOyF42pPu01lXExBBmCTN22qZ5djVc3KLBIK4rq 7wh1Lm6WhfQyLYAUMzB772alh393kF23pQjlFXiTJld4lNqsVFQN2t8qcz8jaaD81D59 f4JQ== 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=4mML9AZRAymo7tIoMyn6vvoJJGVxJDy1ivc2/cUpfQw=; b=tzWm+oV1UNHx96mkp/l01XW0YCznj19mW0b7sTg0b9lDwmmKRUsKClHbyWI/BhaPIW 0DXFS2r8KaRmtXhdTFzWHaXAhvJwCQVpMJ8JhhAcwYGwnNrSKyIASCSXVWeXjjlQZS3s q7iswdq1vY25VxvSr9Yp+RjndeRQrvga2apd+xHmK9NRMmnGXntCfzLIc27SeriFunqS GaUysok1yCuOjKav7hiQf3SumtHMet/USj94RPkcXnMLvjPGk3adAhSKzyl7+Z5Lrlu8 tuamy8UavgpNZA9NQeVKNhJkW2fXVq2zmvBCbXX2j+fHX6YUAaL6VolcjeLv83I0N+ic fseg== 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 k7si18430357edb.265.2019.11.20.05.22.20; Wed, 20 Nov 2019 05:22:44 -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 S1728858AbfKTKti (ORCPT + 99 others); Wed, 20 Nov 2019 05:49:38 -0500 Received: from foss.arm.com ([217.140.110.172]:37176 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728760AbfKTKti (ORCPT ); Wed, 20 Nov 2019 05:49:38 -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 7FBDA1FB; Wed, 20 Nov 2019 02:49:37 -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 9B6D73F6C4; Wed, 20 Nov 2019 02:49:36 -0800 (PST) Date: Wed, 20 Nov 2019 10:49:34 +0000 From: Qais Yousef To: Thomas Gleixner Cc: Greg Kroah-Hartman , Tony Luck , Fenghua Yu , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 04/12] ia64: Replace cpu_down with freeze_secondary_cpus Message-ID: <20191120104933.e6gkdjwkzulm6uak@e107158-lin.cambridge.arm.com> References: <20191030153837.18107-1-qais.yousef@arm.com> <20191030153837.18107-5-qais.yousef@arm.com> <20191119223234.ov323rcln4slj7br@e107158-lin.cambridge.arm.com> <20191119231912.viwqgcyzttoo5eou@e107158-lin.cambridge.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/20/19 09:46, Thomas Gleixner wrote: > On Tue, 19 Nov 2019, Qais Yousef wrote: > > On 11/19/19 23:59, Thomas Gleixner wrote: > > > On Tue, 19 Nov 2019, Qais Yousef wrote: > > > > My plan was to simply make freeze_secondary_cpus() available and protected by > > > > CONFIG_SMP only instead. > > > > > > > > Good plan? > > > > > > No. freeze_secondary_cpus() is really for hibernation. Look at the exit > > > conditions there. > > > > Hmm do you mean the pm_wakeup_pending() abort? > > > > In arm64 we machine_shutdown() calls disable_nonboot_cpus(), which in turn > > a wrapper around freeze_secondary_cpus() with 0 passed as an argument. > > > > IIUC this means arm64 could fail to offline all CPUs on machine_shutdown(), > > correct? > > Looks like. Okay I'll double check and introduce a new function to be called from machine_down() for arm64 and ia64 if necessary. Thanks -- Qais Yousef