[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241029065319.zto3wlvceec3fjym@vireshk-i7>
Date: Tue, 29 Oct 2024 12:23:19 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Beata Michalska <beata.michalska@....com>
Cc: Vanshidhar Konda <vanshikonda@...amperecomputing.com>,
Sumit Gupta <sumitg@...dia.com>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-pm@...r.kernel.org,
ionela.voinescu@....com, sudeep.holla@....com, will@...nel.org,
catalin.marinas@....com, rafael@...nel.org,
yang@...amperecomputing.com, lihuisong@...wei.com,
zhanjie9@...ilicon.com, linux-tegra <linux-tegra@...r.kernel.org>,
Bibek Basu <bbasu@...dia.com>
Subject: Re: [PATCH v7 3/4] arm64: Provide an AMU-based version of
arch_freq_avg_get_on_cpu
On 10-10-24, 13:08, Beata Michalska wrote:
> That is a fair point but I am not entirely convinced using '0' instead makes
> things any more clearer as this is in no way a valid CPU frequency.
> As long as we document the expected behaviour keeping the interface well
> defined, both options should be fine I guess.
>
> @Viresh: what is your opinion on that one ?
Failing to get frequency for the CPU shouldn't be represented by 0,
even if it is confusing for the user.
--
viresh
Powered by blists - more mailing lists