[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAH6sp9PvCySowA=+uLe9NZ542GvaF=0Yad43=Bw2z7GEfutshA@mail.gmail.com>
Date: Wed, 15 Apr 2015 08:32:56 +0200
From: Frans Klaver <fransklaver@...il.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
Ingo Molnar <mingo@...nel.org>,
Preeti U Murthy <preeti@...ux.vnet.ibm.com>,
Viresh Kumar <viresh.kumar@...aro.org>,
Marcelo Tosatti <mtosatt@...hat.com>,
Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [patch 02/39] hrtimer: Get rid of the resolution field in hrtimer_clock_base
On Wed, Apr 15, 2015 at 8:29 AM, Frans Klaver <fransklaver@...il.com> wrote:
> On Tue, Apr 14, 2015 at 11:08 PM, Thomas Gleixner <tglx@...utronix.de> wrote:
>> The field has no value because all clock bases have the same
>> resolution. The resolution only changes when we switch to high
>> resolution timer mode. We can evaluate that from a single static
>> variable as well. In the !HIGHRES case its simply a constant.
>>
>> Export the variable, so we can simplify the usage sites.
>
> There seems to be only one usage site outside hrtimer.c itself. That
> one only reads the value.
OK, this is incorrect. Still, if it's only meant to be read from
outside hrtimer.c:
> Wouldn't it make sense to keep the variable
> from the interface and use a read function instead?
Thanks,
Frans
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists