From: Vincenzo Frascino <vincenzo.frascino@arm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>, Shuah Khan <shuah@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH v2 0/4] kselftest: Extend vDSO tests
Date: Tue, 5 May 2020 16:11:06 +0100 [thread overview]
Message-ID: <e59bd06b-188c-c3c4-859e-3ced3ea0bb69@arm.com> (raw)
In-Reply-To: <CAK8P3a0hUG3-21=HCrxxjQSxFJsDBu704NQCiOW6jNpZV5Ns8w@mail.gmail.com>
Hi Arnd,
On 5/5/20 4:07 PM, Arnd Bergmann wrote:
> On Tue, May 5, 2020 at 5:03 PM Vincenzo Frascino
> <vincenzo.frascino@arm.com> wrote:
>> On 5/5/20 3:50 PM, Arnd Bergmann wrote:
>>> On Wed, Apr 29, 2020 at 1:34 PM Vincenzo Frascino <vincenzo.frascino@arm.com> wrote:
>>>
>>> Not sure if you are aware of the recent bug report about clock_gettime64()
>>> returning invalid times on some arm32 kernels:
>>> https://github.com/raspberrypi/linux/issues/3579
>>>
>>
>> No, I was not aware of the problem. There has been no mention on the arm list
>> (unless I missed it). I can try to have a look at it as soon as I get some time.
>
> Right, it was on only on the musl list, and I had pinged you on IRC, but you
> must have been offline.
>
Sorry about that, I did not get your message :( The only thing I can think it is
that if it was last to last week, I was on holiday... Anyway thanks for pointing
this out.
>>> Regardless of when that gets fixed or by whom, I wonder if kselftest should
>>> also check for consistency, i.e. call both the vdso and the syscall version of
>>> clock_gettime() and clock_gettime64() and check that the results are always
>>> in sequence.
>>>
>>
>> The test #4 partially does that: it calls syscall-vdso-syscall and verifies that
>> the sequencing is correct. I reused the x86 code for that. I could extend it to
>> clock_gettime64() and make sure it builds on all the platforms.
>
> Sounds good to me.
>
> Arnd
>
--
Regards,
Vincenzo
prev parent reply other threads:[~2020-05-05 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 11:28 [PATCH v2 0/4] kselftest: Extend vDSO tests Vincenzo Frascino
2020-04-29 11:28 ` [PATCH v2 1/4] kselftest: Enable vDSO test on non x86 platforms Vincenzo Frascino
2020-04-29 11:28 ` [PATCH v2 2/4] kselftest: Extend vDSO selftest Vincenzo Frascino
2020-04-29 11:28 ` [PATCH v2 3/4] kselftest: Extend vDSO selftest to clock_getres Vincenzo Frascino
2020-04-29 11:28 ` [PATCH v2 4/4] kselftest: Move test_vdso to the vDSO test suite Vincenzo Frascino
2020-05-05 14:50 ` [PATCH v2 0/4] kselftest: Extend vDSO tests Arnd Bergmann
2020-05-05 15:04 ` Vincenzo Frascino
2020-05-05 15:07 ` Arnd Bergmann
2020-05-05 15:11 ` Vincenzo Frascino [this message]
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=e59bd06b-188c-c3c4-859e-3ced3ea0bb69@arm.com \
--to=vincenzo.frascino@arm.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).