public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
	linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Paul Mackerras <paulus@samba.org>,
	Greentime Hu <green.hu@gmail.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Vincent Chen <deanbo422@gmail.com>, Shuah Khan <shuah@kernel.org>
Subject: Re: [PATCH 2/5] powerpc: Fix vDSO clock_getres()
Date: Tue, 2 Apr 2019 10:00:25 +0100	[thread overview]
Message-ID: <f4919c8a-e0dd-ab78-d6a3-b792fa388aa9@arm.com> (raw)
In-Reply-To: <f54a24fe-f893-10c9-9177-4985bad2e745@c-s.fr>

Hi Christophe,

thank you for your review.

On 02/04/2019 06:54, Christophe Leroy wrote:
> 
> 
> On 04/01/2019 11:51 AM, 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 powerpc vdso implementation of clock_getres keeping a copy of
>> hrtimer_resolution in vdso data and using that directly.
>>
>> Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
>> Cc: Paul Mackerras <paulus@samba.org>
>> Cc: Michael Ellerman <mpe@ellerman.id.au>
>> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm.com>
>> ---
>>   arch/powerpc/include/asm/vdso_datapage.h  |  2 ++
> 
> Conflicts with commit b5b4453e7912 ("powerpc/vdso64: Fix CLOCK_MONOTONIC 
> inconsistencies across Y2038")
> 

Thanks for pointing this out, I will rebase my code on top of the latest version
before reissuing v2.

...

-- 
Regards,
Vincenzo

  parent reply	other threads:[~2019-04-02  9:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 11:51 [PATCH 0/5] Fix vDSO clock_getres() Vincenzo Frascino
2019-04-01 11:51 ` Vincenzo Frascino
2019-04-01 11:51 ` [PATCH 1/5] arm64: " Vincenzo Frascino
2019-04-01 11:51   ` Vincenzo Frascino
2019-04-15 17:35   ` Catalin Marinas
2019-04-15 17:35     ` Catalin Marinas
2019-04-16 12:42     ` Vincenzo Frascino
2019-04-16 12:42       ` Vincenzo Frascino
2019-04-16 14:23       ` Will Deacon
2019-04-16 14:23         ` Will Deacon
2019-04-01 11:51 ` [PATCH 2/5] powerpc: " Vincenzo Frascino
2019-04-01 11:51   ` Vincenzo Frascino
2019-04-02  5:54   ` Christophe Leroy
2019-04-02  5:54     ` Christophe Leroy
2019-04-02  9:00     ` Vincenzo Frascino [this message]
2019-04-02  9:00       ` Vincenzo Frascino
2019-04-02  6:14   ` Christophe Leroy
2019-04-02  6:14     ` Christophe Leroy
2019-04-02  9:01     ` Vincenzo Frascino
2019-04-02  9:01       ` Vincenzo Frascino
2019-04-01 11:51 ` [PATCH 3/5] s390: " Vincenzo Frascino
2019-04-01 11:51   ` Vincenzo Frascino
2019-04-03  9:38   ` Martin Schwidefsky
2019-04-03  9:38     ` Martin Schwidefsky
2019-04-03 10:06     ` Thomas Gleixner
2019-04-03 10:06       ` Thomas Gleixner
2019-04-03 14:21       ` Vincenzo Frascino
2019-04-03 14:21         ` Vincenzo Frascino
2019-04-01 11:51 ` [PATCH 4/5] nds32: " Vincenzo Frascino
2019-04-01 11:51   ` Vincenzo Frascino
2019-04-01 11:51 ` [PATCH 5/5] kselftest: Extend vDSO selftest to clock_getres Vincenzo Frascino
2019-04-01 11:51   ` Vincenzo Frascino

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f4919c8a-e0dd-ab78-d6a3-b792fa388aa9@arm.com \
    --to=vincenzo.frascino@arm.com \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=deanbo422@gmail.com \
    --cc=green.hu@gmail.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@samba.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox