From: Davidlohr Bueso <dave@stgolabs.net>
To: Alistair Francis <alistair.francis@opensource.wdc.com>
Cc: linux-riscv@lists.infradead.org,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
alistair23@gmail.com, namhyung@kernel.org, jolsa@redhat.com,
alexander.shishkin@linux.intel.com, mark.rutland@arm.com,
acme@kernel.org, dvhart@infradead.org, peterz@infradead.org,
mingo@redhat.com, tglx@linutronix.de, atish.patra@wdc.com,
arnd@arndb.de, Alistair Francis <alistair.francis@wdc.com>
Subject: Re: [PATCH v3 1/2] perf benchmark: Call the futex syscall from a function
Date: Fri, 17 Sep 2021 11:21:13 -0700 [thread overview]
Message-ID: <20210917182113.nacg5zbjiexmhhjk@offworld> (raw)
In-Reply-To: <20210917061040.2270822-1-alistair.francis@opensource.wdc.com>
On Fri, 17 Sep 2021, Alistair Francis wrote:
>From: Alistair Francis <alistair.francis@wdc.com>
>
>In preparation for a more complex futex() function let's convert the
>current macro into two functions. We need two functions to avoid
>compiler failures as the macro is overloaded.
>
>This will allow us to include pre-processor conditionals in the futex
>syscall functions.
>
>Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Acked-by: Davidlohr Bueso <dbueso@suse.de>
prev parent reply other threads:[~2021-09-17 18:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 6:10 [PATCH v3 1/2] perf benchmark: Call the futex syscall from a function Alistair Francis
2021-09-17 6:10 ` [PATCH v3 2/2] perf bench: Add support for 32-bit systems with 64-bit time_t Alistair Francis
2021-09-17 7:33 ` Arnd Bergmann
2021-09-17 18:33 ` Davidlohr Bueso
2021-09-20 22:47 ` André Almeida
2021-09-21 8:08 ` Arnd Bergmann
2021-09-21 23:06 ` André Almeida
2021-09-22 11:26 ` Arnd Bergmann
2021-09-22 11:27 ` Arnd Bergmann
2021-09-24 4:34 ` Alistair Francis
2021-09-24 4:34 ` Alistair Francis
2021-09-26 21:32 ` André Almeida
2021-09-17 18:21 ` Davidlohr Bueso [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=20210917182113.nacg5zbjiexmhhjk@offworld \
--to=dave@stgolabs.net \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=alistair.francis@opensource.wdc.com \
--cc=alistair.francis@wdc.com \
--cc=alistair23@gmail.com \
--cc=arnd@arndb.de \
--cc=atish.patra@wdc.com \
--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).