From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martin Schwidefsky Subject: Re: [PATCH 3/5] s390: Fix vDSO clock_getres() Date: Wed, 3 Apr 2019 11:38:44 +0200 Message-ID: <20190403113844.334a32d9@mschwideX1> References: <20190401115152.32751-1-vincenzo.frascino@arm.com> <20190401115152.32751-4-vincenzo.frascino@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190401115152.32751-4-vincenzo.frascino@arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org List-Archive: List-Post: To: Vincenzo Frascino Cc: linux-arch@vger.kernel.org, linux-s390@vger.kernel.org, Shuah Khan , Arnd Bergmann , Heiko Carstens , Catalin Marinas , Will Deacon , Paul Mackerras , Michael Ellerman , Benjamin Herrenschmidt , Thomas Gleixner , Vincent Chen , linuxppc-dev@lists.ozlabs.org, linux-arm-kernel@lists.infradead.org, Greentime Hu List-ID: On Mon, 1 Apr 2019 12:51:50 +0100 Vincenzo Frascino wrote: > clock_getres in the vDSO library has to preserve the same behaviour > of posix_get_hrtimer_res(). > > In particular, posix_get_hrtimer_res() does: > sec = 0; > ns = hrtimer_resolution; > and hrtimer_resolution depends on the enablement of the high > resolution timers that can happen either at compile or at run time. > > Fix the s390 vdso implementation of clock_getres keeping a copy of > hrtimer_resolution in vdso data and using that directly. > > Cc: Martin Schwidefsky > Cc: Heiko Carstens > Signed-off-by: Vincenzo Frascino > --- > arch/s390/include/asm/vdso.h | 1 + > arch/s390/kernel/asm-offsets.c | 2 +- > arch/s390/kernel/time.c | 1 + > arch/s390/kernel/vdso32/clock_getres.S | 17 ++++++++++++----- > arch/s390/kernel/vdso64/clock_getres.S | 15 ++++++++++----- > 5 files changed, 25 insertions(+), 11 deletions(-) I tried this patch and in principle this works. In that regard Acked-by: Martin Schwidefsky But I wonder if the loop to check the update counter is really necessary. The hrtimer_resolution value can only changes once with the first call to hrtimer_switch_to_hres(). With the TOD clock as the only clock available on s390 we always have the ability to do hrtimer. It then all depends on the highres=[on|off] kernel parameter what value we get with clock_getres(). -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.