linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@kernel.org>
To: Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: LKML <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 2/3] kselftest: Extend vDSO selftest
Date: Tue, 24 Mar 2020 10:22:18 -0700	[thread overview]
Message-ID: <CALCETrUPaJCgY_herAUJAfqUbXS6S9xOaLz9abFEWOjEouNf+A@mail.gmail.com> (raw)
In-Reply-To: <20200324145120.42194-3-vincenzo.frascino@arm.com>

On Tue, Mar 24, 2020 at 7:51 AM Vincenzo Frascino
<vincenzo.frascino@arm.com> wrote:
>
> The current version of the multiarch vDSO selftest verifies only
> gettimeofday.
>
> Extend the vDSO selftest to the other library functions:
>  - time
>  - clock_getres
>  - clock_gettime
>
> The extension has been used to verify the unified vdso library on the
> supported architectures.

The code in tools/testing/selftests/x86/test_vdso.c actually checks
that the times returned by the vDSO are correct.  Perhaps that code
should be copied or moved here?

  reply	other threads:[~2020-03-24 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 14:51 [PATCH 0/3] kselftest: Extend vDSO tests Vincenzo Frascino
2020-03-24 14:51 ` [PATCH 1/3] kselftest: Enable vDSO test on non x86 platforms Vincenzo Frascino
2020-03-24 14:51 ` [PATCH 2/3] kselftest: Extend vDSO selftest Vincenzo Frascino
2020-03-24 17:22   ` Andy Lutomirski [this message]
2020-03-25 13:44     ` Vincenzo Frascino
2020-03-24 14:51 ` [PATCH 3/3] kselftest: Extend vDSO selftest to clock_getres 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=CALCETrUPaJCgY_herAUJAfqUbXS6S9xOaLz9abFEWOjEouNf+A@mail.gmail.com \
    --to=luto@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincenzo.frascino@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;
as well as URLs for NNTP newsgroup(s).