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 0/6] Fixup perf tests for 32-bit systems with 64-bit time_t
Date: Fri, 28 Oct 2022 19:56:26 +1000 [thread overview]
Message-ID: <20221028095632.1081262-1-alistair.francis@opensource.wdc.com> (raw)
From: Alistair Francis <alistair.francis@wdc.com>
This series aims to fix perf for 32-bit systems with a 64-bit time_t
(like RV32).
This series also adds a public futex waitv syscall that userspace
can use to avoid this complexity.
This series hasn't addressed the build failure pointed out in:
https://patchwork.kernel.org/project/linux-riscv/patch/20211209235857.423773-1-alistair.francis@opensource.wdc.com/
as I'm unable to reproduce it and unclear on how it can be fixed.
v6:
- No change
Alistair Francis (6):
perf bench futex: Add support for 32-bit systems with 64-bit time_t
selftests: futex: Call the futex syscall from a function
uapi: futex: Add a futex syscall
selftests: futex: Add support for 32-bit systems with 64-bit time_t
uapi: futex: Add a futex waitv syscall
selftests: futex: Use futex_waitv helper function
include/uapi/linux/futex_syscall.h | 119 ++++++++++++++++++
tools/perf/bench/futex.h | 52 +++++++-
.../futex/functional/futex_requeue_pi.c | 2 +-
.../selftests/futex/include/futex2test.h | 3 +-
.../selftests/futex/include/futextest.h | 60 +++++----
5 files changed, 206 insertions(+), 30 deletions(-)
create mode 100644 include/uapi/linux/futex_syscall.h
--
2.37.3
next 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 Alistair Francis [this message]
2022-10-28 9:56 ` [PATCH 1/6] perf bench futex: Add support for 32-bit systems with 64-bit time_t 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 ` [PATCH 6/6] selftests: futex: Use futex_waitv helper function Alistair Francis
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-1-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).