Received: by 2002:a05:6a10:d5a5:0:0:0:0 with SMTP id gn37csp246596pxb; Thu, 30 Sep 2021 05:20:09 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxFhIcbg+E0mVIGfjBZ1MUp5vOMzpq/feZQSYq6hQTEGL6sPAzH8mJgSCR626cJ25qGVryG X-Received: by 2002:a63:7c5c:: with SMTP id l28mr4640075pgn.73.1633004408887; Thu, 30 Sep 2021 05:20:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1633004408; cv=none; d=google.com; s=arc-20160816; b=o0DWdOugaEtU6GmnhJGBx2ZYq2Vd7/AJ/Rs+NWHRb0zjrsic+kBgxJh/71HiyObBAv j6z1wiquwJ97NRDEHUks2BbP8VF+XWO6HV7483wYL+ssmFeQkUgsKMW+FiZzoJxZGTMG nzNGDSQCZUlO2l9flvWFpTPyMtg/VSFXwOEFbj2oxHHddv9GbOEJBkIoC3y1fb/ZZ0yI dQyT8cQZsRwwTaDrFoE/JzD4C9nvgKGA2Y6sgRUMHj6mg2rLU9/4+sYeOepBRWomIaoE p6JYuRyMBjDRLafqHyrD8tDqlMquuxCsMr3LdIdRFxpa8ySoVImzkFC3DUwfWtJC7q63 bIPw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:cc :references:to:subject; bh=Kq6CmxRpjOZKXFoLhqgSpl/xwrc76wNtzzOPEdwLVTA=; b=YFZtmYwfaE3nrp4HHCATfpNaSEma3YyF53O/w8hhui2SstVgmC9PREZ9SVZSLSxyjK SqazJnxSariKNJhAE7nBUyfwAmsaDifI8dA2jiuCCmI5eX5qR5WwmjU2LGFpQnRzzXvc rl7axcRlHkMYzDNutIImjOddDOaQYkfy8nkmHg44ZUJpuUQfNKYnfvT07PmoMKZRjoX3 1IEQhZVoB+Wxc/wZX1X6Qe9NIvQzAbwM9r/c9PBGvW7a6te73L+pAkcf15kovfuzarnJ nIFjYVv47UQNKN9yQeX2ewXJEwoqzkbLar3pIxwphc3jKaRLLhbcg6OWCI/rcwgMuyBm hsXQ== 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=arm.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i10si3288234pgp.630.2021.09.30.05.19.51; Thu, 30 Sep 2021 05:20:08 -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=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1349803AbhI3KLs (ORCPT + 99 others); Thu, 30 Sep 2021 06:11:48 -0400 Received: from foss.arm.com ([217.140.110.172]:51728 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1349795AbhI3KLp (ORCPT ); Thu, 30 Sep 2021 06:11:45 -0400 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 5E65F106F; Thu, 30 Sep 2021 03:10:02 -0700 (PDT) Received: from [10.57.21.60] (unknown [10.57.21.60]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 720433F793; Thu, 30 Sep 2021 03:10:01 -0700 (PDT) Subject: Re: [RFD] Remove the userspace governor and the cooling device set state sysfs entry To: Daniel Lezcano References: Cc: Zhang Rui , "Rafael J. Wysocki" , Linux Kernel Mailing List , Linux PM mailing list From: Lukasz Luba Message-ID: <39728f24-7781-543c-ad28-fd1c7552d96a@arm.com> Date: Thu, 30 Sep 2021 11:10:00 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Daniel, On 9/22/21 10:59 AM, Daniel Lezcano wrote: > > Hi, > > the userspace governor is sending temperature when polling is active and > trip point crossed events. Nothing else. > > In the other side, the cooling device have their cooling device > set_cur_state read-writable all the time. > > The thermal framework is wrongly used by userspace as a power capping > framework by acting on the cooling device opaque state. This one then > competes with the in-kernel governor decision. > > As the new netlink thermal notification is able to provide the same > information than the userspace governor. > > I propose to remove the userspace governor and the cur_state entry in > the sysfs exported file. > > The DTPM framework is the right framework to do power capping and > moreover it deals with the aggregation via the dev pm qos. > > Does it make sense ? It sounds that we should be OK with the information from netlink. I don't see objections. We can also extend the netlink packet when needed. I'm fine with removing the user-space governor. Regards, Lukasz