From: Quentin Perret <quentin.perret@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
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
Date: Wed, 15 May 2019 10:17:01 +0100 [thread overview]
Message-ID: <20190515091658.sbpg6qiovhtblqyr@queper01-lin> (raw)
In-Reply-To: <0ced18eb-e424-fe6b-b11e-165a3c108170@linaro.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 <viresh.kumar@linaro.org>
> > Signed-off-by: Quentin Perret <quentin.perret@arm.com>
>
> 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
next prev parent reply other threads:[~2019-05-15 9:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 8:23 [PATCH v4 0/3] Make IPA use PM_EM Quentin Perret
2019-05-15 8:23 ` Quentin Perret
2019-05-15 8:23 ` [PATCH v4 1/3] arm64: defconfig: Enable CONFIG_ENERGY_MODEL Quentin Perret
2019-05-15 8:23 ` Quentin Perret
2019-05-15 8:46 ` Daniel Lezcano
2019-05-15 8:46 ` Daniel Lezcano
2019-05-15 9:22 ` Quentin Perret
2019-05-15 9:22 ` Quentin Perret
2019-05-15 8:23 ` [PATCH v4 2/3] PM / EM: Expose perf domain struct Quentin Perret
2019-05-15 8:23 ` Quentin Perret
2019-05-15 9:06 ` Daniel Lezcano
2019-05-15 9:06 ` Daniel Lezcano
2019-05-15 9:17 ` Quentin Perret [this message]
2019-05-15 9:17 ` Quentin Perret
2019-05-15 9:56 ` Daniel Lezcano
2019-05-15 9:56 ` Daniel Lezcano
2019-05-15 10:07 ` Quentin Perret
2019-05-15 10:07 ` Quentin Perret
2019-05-15 10:16 ` Daniel Lezcano
2019-05-15 10:16 ` Daniel Lezcano
2019-05-15 10:22 ` Viresh Kumar
2019-05-15 10:22 ` Viresh Kumar
2019-05-15 10:40 ` Quentin Perret
2019-05-15 10:40 ` Quentin Perret
2019-05-15 10:46 ` Quentin Perret
2019-05-15 10:46 ` Quentin Perret
2019-05-15 10:51 ` Daniel Lezcano
2019-05-15 10:51 ` Daniel Lezcano
2019-05-15 11:01 ` Quentin Perret
2019-05-15 11:01 ` Quentin Perret
2019-05-15 11:07 ` Daniel Lezcano
2019-05-15 11:07 ` Daniel Lezcano
2019-05-15 10:54 ` Daniel Lezcano
2019-05-15 10:54 ` Daniel Lezcano
2019-05-15 10:57 ` Quentin Perret
2019-05-15 10:57 ` Quentin Perret
2019-05-15 8:23 ` [PATCH v4 3/3] thermal: cpu_cooling: Migrate to using the EM framework Quentin Perret
2019-05-15 8:23 ` Quentin Perret
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190515091658.sbpg6qiovhtblqyr@queper01-lin \
--to=quentin.perret@arm.com \
--cc=amit.kachhap@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=edubezval@gmail.com \
--cc=ionela.voinescu@arm.com \
--cc=javi.merino@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mka@chromium.org \
--cc=rjw@rjwysocki.net \
--cc=rui.zhang@intel.com \
--cc=viresh.kumar@linaro.org \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox