From: Michael Ellerman <mpe@ellerman•id.au>
To: Vincenzo Frascino <vincenzo.frascino@arm•com>,
linux-arch@vger•kernel.org, linuxppc-dev@lists•ozlabs.org,
linux-s390@vger•kernel.org, linux-kselftest@vger•kernel.org
Cc: Arnd Bergmann <arnd@arndb•de>,
Heiko Carstens <heiko.carstens@de•ibm.com>,
Paul Mackerras <paulus@samba•org>,
Martin Schwidefsky <schwidefsky@de•ibm.com>,
Thomas Gleixner <tglx@linutronix•de>,
vincenzo.frascino@arm•com, Shuah Khan <shuah@kernel•org>
Subject: Re: [PATCH v4 3/3] kselftest: Extend vDSO selftest to clock_getres
Date: Tue, 28 May 2019 16:19:21 +1000 [thread overview]
Message-ID: <87lfyrp0d2.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20190523112116.19233-4-vincenzo.frascino@arm.com>
Vincenzo Frascino <vincenzo.frascino@arm•com> writes:
> The current version of the multiarch vDSO selftest verifies only
> gettimeofday.
>
> Extend the vDSO selftest to clock_getres, to verify that the
> syscall and the vDSO library function return the same information.
>
> The extension has been used to verify the hrtimer_resoltion fix.
This is passing for me even without patch 1 applied, shouldn't it fail
without the fix? What am I missing?
# uname -r
5.2.0-rc2-gcc-8.2.0
# ./vdso_clock_getres
clock_id: CLOCK_REALTIME [PASS]
clock_id: CLOCK_BOOTTIME [PASS]
clock_id: CLOCK_TAI [PASS]
clock_id: CLOCK_REALTIME_COARSE [PASS]
clock_id: CLOCK_MONOTONIC [PASS]
clock_id: CLOCK_MONOTONIC_RAW [PASS]
clock_id: CLOCK_MONOTONIC_COARSE [PASS]
cheers
> Cc: Shuah Khan <shuah@kernel•org>
> Signed-off-by: Vincenzo Frascino <vincenzo.frascino@arm•com>
> ---
>
> Note: This patch is independent from the others in this series, hence it
> can be merged singularly by the kselftest maintainers.
>
> tools/testing/selftests/vDSO/Makefile | 2 +
> .../selftests/vDSO/vdso_clock_getres.c | 124 ++++++++++++++++++
> 2 files changed, 126 insertions(+)
> create mode 100644 tools/testing/selftests/vDSO/vdso_clock_getres.c
next prev parent reply other threads:[~2019-05-28 6:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 11:21 [PATCH v4 0/3] Fix vDSO clock_getres() Vincenzo Frascino
2019-05-23 11:21 ` [PATCH v4 1/3] powerpc: " Vincenzo Frascino
2019-05-29 13:14 ` Sasha Levin
2019-05-23 11:21 ` [PATCH v4 2/3] s390: " Vincenzo Frascino
2019-05-23 11:21 ` [PATCH v4 3/3] kselftest: Extend vDSO selftest to clock_getres Vincenzo Frascino
2019-05-28 6:19 ` Michael Ellerman [this message]
2019-05-28 11:57 ` Vincenzo Frascino
2019-05-28 17:01 ` Christophe Leroy
2019-05-28 17:05 ` Vincenzo Frascino
2019-06-04 13:16 ` Christophe Leroy
2019-06-04 13:32 ` Vincenzo Frascino
2019-06-04 13:39 ` Christophe Leroy
2019-06-04 13:43 ` Vincenzo Frascino
2019-06-04 13:52 ` Christophe Leroy
2019-06-04 14:21 ` Vincenzo Frascino
2019-06-13 15:22 ` 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=87lfyrp0d2.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=arnd@arndb$(echo .)de \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kselftest@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=paulus@samba$(echo .)org \
--cc=schwidefsky@de$(echo .)ibm.com \
--cc=shuah@kernel$(echo .)org \
--cc=tglx@linutronix$(echo .)de \
--cc=vincenzo.frascino@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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