Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp344886yba; Wed, 15 May 2019 02:20:21 -0700 (PDT) X-Google-Smtp-Source: APXvYqykDTqU1UbVqDgCaoi5IdxPnEWrQH1BqymAOXq7d2X6R2pW3a0EWXWWq1FeEa/VchZuXdcd X-Received: by 2002:a63:c02:: with SMTP id b2mr26420643pgl.5.1557912021007; Wed, 15 May 2019 02:20:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557912020; cv=none; d=google.com; s=arc-20160816; b=GROPWAG7sUXalckuLsH78jPE9nY7UesFieA64dYESZg3SJP8hxmPUjWeWMAu7KyLRm 13G5TNlyHeTRRdY7wd9KUpLf5pSk6PExThJY0yJaLTN0awhdnKt1rjKPnaCM9EL+YS2W mEnaub7jnMVkaM0jzGpgpY8wjLgx7ky/aGm7k67CVGWtaX26qk8JB9kWHJArPT7mnujD Ajqx5sOJvIJqyzny+/ZNlrjtF1Ym7i0uj1H0vxC6O/tcbBDag55BJ3IHqUIKcDmEa09w IoM6ZBT5bd5Rh6+nshoQxakYnFxt/YmIm9lkb+ky1RI5IWGc8I1bm8O55+7OuLk4SjZz nRyA== 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=hueZKixSrDtOcC5yXtXrnA/yQzos9Oswmi20r4AC7s4=; b=K6jL3ibYtWVoN1f5incKkhq8HDfs2w0xBoIfABLbIJSvAOHhf5NbrVC4lniZAySIiW Yw71T2X08bXBkSwiFfuBmY90aSNoNTPm9rUaaY8XuGuTOQPPSGmqjGL3m9JEum2jErhg knpMtTDU3L7UroGTKenCKeJpb99XpMlFg+IysZ7gvXxcqPmZSJqamq2d01BO+18ZhYrn F9zcUv0wISmCzwNfwFrg/O+nL4H4qhOr+ADORRj4nZJKlvz67oyuOTlAANWgwUUc58qA bblf500KbjfYPD8W8kIaA4fhKPt9ySY/9561ecvTrtB0wN25dxXjBYMsrklGdLjE6VqS ep6w== 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 19si1315956pgu.457.2019.05.15.02.20.06; Wed, 15 May 2019 02:20:20 -0700 (PDT) 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 S1726381AbfEOJRG (ORCPT + 99 others); Wed, 15 May 2019 05:17:06 -0400 Received: from foss.arm.com ([217.140.101.70]:38820 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725912AbfEOJRF (ORCPT ); Wed, 15 May 2019 05:17:05 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 4B06D341; Wed, 15 May 2019 02:17:05 -0700 (PDT) Received: from queper01-lin (queper01-lin.cambridge.arm.com [10.1.195.48]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id BA3A53F703; Wed, 15 May 2019 02:17:02 -0700 (PDT) Date: Wed, 15 May 2019 10:17:01 +0100 From: Quentin Perret To: Daniel Lezcano Cc: edubezval@gmail.com, rui.zhang@intel.com, javi.merino@kernel.org, viresh.kumar@linaro.org, amit.kachhap@gmail.com, rjw@rjwysocki.net, will.deacon@arm.com, catalin.marinas@arm.com, dietmar.eggemann@arm.com, ionela.voinescu@arm.com, mka@chromium.org, linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v4 2/3] PM / EM: Expose perf domain struct Message-ID: <20190515091658.sbpg6qiovhtblqyr@queper01-lin> References: <20190515082318.7993-1-quentin.perret@arm.com> <20190515082318.7993-3-quentin.perret@arm.com> <0ced18eb-e424-fe6b-b11e-165a3c108170@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0ced18eb-e424-fe6b-b11e-165a3c108170@linaro.org> User-Agent: NeoMutt/20171215 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Daniel, On Wednesday 15 May 2019 at 11:06:18 (+0200), Daniel Lezcano wrote: > On 15/05/2019 10:23, Quentin Perret wrote: > > In the current state, the perf_domain struct is fully defined only when > > CONFIG_ENERGY_MODEL=y. Since we need to write code that compiles both > > with or without that option in the thermal framework, make sure to > > actually define the struct regardless of the config option. That allows > > to avoid using stubbed accessor functions all the time in code paths > > that use the EM. > > > > Acked-by: Viresh Kumar > > Signed-off-by: Quentin Perret > > This patch implies the cpu cooling device can be set without the energy > model. > > Isn't it possible to make a strong dependency for the cpu cooling device > on the energy model option, add the energy model as default on arm arch > and drop this patch? Right, that should work too. > After all, the cpu cooling is using the em framework. The reason I did it that way is simply to keep things flexible. If you don't compile in THERMAL_GOV_POWER_ALLOCATOR, you will never use the EM for CPU thermal. So I thought it would be good to not mandate compiling in ENERGY_MODEL in this case -- that should save a bit of space. But TBH I don't have a strong opinion on this one, so if everybody agrees it's fine to just make CPU_THERMAL depend on ENERGY_MODEL, I'm happy to drop this patch and fix patch 3/3. That would indeed simplify things a bit. Thanks, Quentin