Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp119896pxb; Wed, 3 Nov 2021 00:53:53 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz/dXcwXnWvF0+h/wlv+cDJ/2+NimEToBwujUs1w+g5YP1QOgG2smk5Ss3xpIXhuhSDmJYu X-Received: by 2002:a05:6602:1545:: with SMTP id h5mr19183935iow.82.1635926032981; Wed, 03 Nov 2021 00:53:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1635926032; cv=none; d=google.com; s=arc-20160816; b=H6bP1pWSiWllRK2lVZhn9ml+aRFS3dpa+I2YC2qso58PAMgCee4izYEE/CvQZ0mw41 +r3sGHCKcKDOIiPVOgMH5UaQwNJ9rrtfu5a/ctmcUpV1BUuwdKOT6E0zzJODA4gusYbU YowIP4YD962xi5KfGLnEirPpaEexAIKH6pH1IMen+TrOH7NA7mmldy1LStTmWpoNHk2m JIhs4HKVXIAIzNG39zTPEpAvJzKjwDp9+Sb2RoEfnfKCSLyrxV97bd0zv9NB6dV7zyyD pwQbNpvXTNTHhOcNgmRlRM01J/3vvrKC5dbqNAL2l6/U04dYxEurfE9s8VrZaXf368os t7SA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:references:cc:to:from :subject; bh=BPAWGfjU3XWLAVzi8eOP7xh9pkNniRg8Q8YmJ+/oBzw=; b=gj7WjMAx7RHajRRn3GYHrz6F/1Zox+tkp5KYxbIQUgkB/YrzTRSoivZCvfAkEshTrT zCr4izTTx6gxVNXxuQV/rWbIgfM8iOMGmqJMR0oM2dj01tQ6xX7+ytVZdc/GI87jRp4W KodqxxJ6CIePGcjhJKcgxM+Ke+qC0h/3aAzshI6RQqyPhO2a4/Y5Pu/NjcU1fQJiBZ/m rDi38zh2DlHiqFziSaWJAfwwrVbWbZP6CMaW/bqwXU9f7la8igA8TJc4NZLWpn+v8lEq LzUOV01zaQgsPlor/gWJ5sVe3U/tmo60sn8Os0epqFhigE+JD8Ftb/sMpJLbDLz9WZz0 cYcg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l6si2784844iow.31.2021.11.03.00.53.25; Wed, 03 Nov 2021 00:53:52 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230431AbhKCHyV (ORCPT + 99 others); Wed, 3 Nov 2021 03:54:21 -0400 Received: from szxga01-in.huawei.com ([45.249.212.187]:14707 "EHLO szxga01-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230046AbhKCHyU (ORCPT ); Wed, 3 Nov 2021 03:54:20 -0400 Received: from dggemv703-chm.china.huawei.com (unknown [172.30.72.57]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4Hkf746QSQzZcgV for ; Wed, 3 Nov 2021 15:49:36 +0800 (CST) Received: from dggpemm500002.china.huawei.com (7.185.36.229) by dggemv703-chm.china.huawei.com (10.3.19.46) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Wed, 3 Nov 2021 15:51:22 +0800 Received: from [10.174.179.5] (10.174.179.5) by dggpemm500002.china.huawei.com (7.185.36.229) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.15; Wed, 3 Nov 2021 15:51:22 +0800 Subject: Re: [Question]: questions about 'Use sysidle detection to let the timekeeper sleep' From: Xiongfeng Wang To: CC: Xie XiuQi , Linux Kernel Mailing List References: <93236de5-f76e-3915-bbdf-9d060435937a@huawei.com> Message-ID: <197f0d3a-dd7c-b90f-4a9d-8a21e289fd6b@huawei.com> Date: Wed, 3 Nov 2021 15:51:21 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <93236de5-f76e-3915-bbdf-9d060435937a@huawei.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.174.179.5] X-ClientProxiedBy: dggems705-chm.china.huawei.com (10.3.19.182) To dggpemm500002.china.huawei.com (7.185.36.229) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sorry, I forgot to Cc the maillist again. Cc it in this mail. On 2021/11/3 10:59, Xiongfeng Wang wrote: > Hi Frederic, > > Sorry to disturb you. It's just that I came across the same problem as you > mentioned in the below link. > https://lwn.net/Articles/577424/ > > This is the problem in my situation. All the CPUs on my machine are in the same > power domain. When nohz_full is enabled, if one of the CPUs keep receiving tick > interrupts, all the CPUs can not be put into powerdown state, even thought all > other CPUs are idle. > > I found your first version patchset in the below link. > https://lore.kernel.org/lkml/1387320692-28460-1-git-send-email-fweisbec@gmail.com/ > But I couldn't found other verions. Even 'full-system-idle' is reverted in the > mailline in the following commit. > commit fe5ac724d81a3c7803e60c2232718f212f3f38d4 > rcu: Remove nohz_full full-system-idle state machine > > I am not sure if we have any other alternative solutions, or do we have rebased > the patchset to mainline kernel. The first version patchset I found is based on > v3.13. > > Thanks, > Xiongfeng >