Andy Lutomirski writes:
> On Thu, Jan 16, 2020 at 12:14 PM Thomas Gleixner wrote:
>> Some architectures have a fixed clocksource which is known at compile
>> time and cannot be replaced or disabled at runtime, e.g. timebase on
>> PowerPC. For such cases the clock mode check in the VDSO code is
>>
On Thu, Jan 16, 2020 at 12:14 PM Thomas Gleixner wrote:
>
> Christophe Leroy writes:
>
> Can you please adjust the prefix for future patches to lib/vdso: and
> start the sentence after the colon with an uppercase letter?
>
> > On arches like POWERPC, the clock is always the timebase, it
>
> Pleas
Christophe Leroy writes:
Can you please adjust the prefix for future patches to lib/vdso: and
start the sentence after the colon with an uppercase letter?
> On arches like POWERPC, the clock is always the timebase, it
Please spell out architectures. Changelogs are not space constraint.
> canno
On arches like POWERPC, the clock is always the timebase, it
cannot be changed on the fly and it is always VDSO capable.
Therefore, give arches the opportunity to redefine the way
clock_mode is checked by moving the check into an overridable
__arch_vdso_capable() macro.
Signed-off-by: Christophe
