[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Z2QKE3uml7CRm0DD@arm.com>
Date: Thu, 19 Dec 2024 12:57:07 +0100
From: Beata Michalska <beata.michalska@....com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: 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, sumitg@...dia.com, yang@...amperecomputing.com,
vanshikonda@...amperecomputing.com, lihuisong@...wei.com,
zhanjie9@...ilicon.com, Jonathan Corbet <corbet@....net>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"H . Peter Anvin" <hpa@...or.com>, Phil Auld <pauld@...hat.com>,
x86@...nel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH v8 1/4] cpufreq: Introduce an optional cpuinfo_avg_freq
sysfs entry
On Wed, Dec 18, 2024 at 09:41:27AM +0530, Viresh Kumar wrote:
> On 17-12-24, 21:10, Beata Michalska wrote:
> > On Tue, Dec 17, 2024 at 09:57:26AM +0530, Viresh Kumar wrote:
> > > On 16-12-24, 23:15, Beata Michalska wrote:
> > > > My bad as I must have misinterpreted that message. Although I am not entirely
> > > > sure why this might be unacceptable as it is not such uncommon approach to use
> > > > signed int space to cover both: expected positive value as well as potential
> > > > error code case failure.
> > >
> > > This part is fine. The problem is with handling frequency here. Signed int can
> > > capture up to 2 GHz of freq, where as unsigned int can capture up to 4 GHz and
> > > so we would really like to keep it at 4 GHz..
> > Right, though the arch_freq_get_on_cpu operates on kHz values.
>
> Hmm.. Missed that.
>
> If you still want to keep it, make that change in a separate patch and
> the new sysfs entry in a different one, so related people can easily
> review.
>
Will do.
Thank you for your feedback. Much appreciated.
---
BR
Beata
> --
> viresh
Powered by blists - more mailing lists