linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alistair Francis <alistair.francis@opensource.wdc.com>
To: linux-kernel@vger.kernel.org
Cc: acme@kernel.org, dave@stgolabs.net,
	alexander.shishkin@linux.intel.com, tglx@linutronix.de,
	namhyung@kernel.org, jolsa@redhat.com,
	linux-perf-users@vger.kernel.org, acme@redhat.com,
	dvhart@infradead.org, mark.rutland@arm.com, peterz@infradead.org,
	arnd@arndb.de, alistair23@gmail.com,
	linux-riscv@lists.infradead.org, mingo@redhat.com,
	alistair.francis@wdc.com, atish.patra@wdc.com
Subject: [PATCH 6/6] selftests: futex: Use futex_waitv helper function
Date: Fri, 28 Oct 2022 19:56:32 +1000	[thread overview]
Message-ID: <20221028095632.1081262-7-alistair.francis@opensource.wdc.com> (raw)
In-Reply-To: <20221028095632.1081262-1-alistair.francis@opensource.wdc.com>

From: Alistair Francis <alistair.francis@wdc.com>

Use the publically exposed __kernel_futex_syscall_waitv() helper
function for the futex_waitv tests.

Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Message-Id: <20211209235857.423773-6-alistair.francis@opensource.wdc.com>
---
 tools/testing/selftests/futex/include/futex2test.h | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/tools/testing/selftests/futex/include/futex2test.h b/tools/testing/selftests/futex/include/futex2test.h
index 9d305520e849..fdc0a0a270cd 100644
--- a/tools/testing/selftests/futex/include/futex2test.h
+++ b/tools/testing/selftests/futex/include/futex2test.h
@@ -5,6 +5,7 @@
  * Copyright 2021 Collabora Ltd.
  */
 #include <stdint.h>
+#include <linux/futex_syscall.h>
 
 #define u64_to_ptr(x) ((void *)(uintptr_t)(x))
 
@@ -18,5 +19,5 @@
 static inline int futex_waitv(volatile struct futex_waitv *waiters, unsigned long nr_waiters,
 			      unsigned long flags, struct timespec *timo, clockid_t clockid)
 {
-	return syscall(__NR_futex_waitv, waiters, nr_waiters, flags, timo, clockid);
+	return __kernel_futex_syscall_waitv(waiters, nr_waiters, flags, timo, clockid);
 }
-- 
2.37.3


      parent reply	other threads:[~2022-10-28  9:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-28  9:56 [PATCH 0/6] Fixup perf tests for 32-bit systems with 64-bit time_t Alistair Francis
2022-10-28  9:56 ` [PATCH 1/6] perf bench futex: Add support " Alistair Francis
2022-10-28  9:56 ` [PATCH 2/6] selftests: futex: Call the futex syscall from a function Alistair Francis
2022-10-28  9:56 ` [PATCH 3/6] uapi: futex: Add a futex syscall Alistair Francis
2022-10-28  9:56 ` [PATCH 4/6] selftests: futex: Add support for 32-bit systems with 64-bit time_t Alistair Francis
2022-10-28  9:56 ` [PATCH 5/6] uapi: futex: Add a futex waitv syscall Alistair Francis
2022-10-28  9:56 ` Alistair Francis [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=20221028095632.1081262-7-alistair.francis@opensource.wdc.com \
    --to=alistair.francis@opensource.wdc.com \
    --cc=acme@kernel.org \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alistair.francis@wdc.com \
    --cc=alistair23@gmail.com \
    --cc=arnd@arndb.de \
    --cc=atish.patra@wdc.com \
    --cc=dave@stgolabs.net \
    --cc=dvhart@infradead.org \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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).