From: Randy Dunlap <rdunlap@infradead.org>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
mikey@neuling.org, hbabu@us.ibm.com, linuxppc-dev@ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] powerpc/ftw: Implement a simple FTW driver
Date: Wed, 17 Jan 2018 10:30:37 -0800 [thread overview]
Message-ID: <e2d57c8c-9667-3b56-8d11-40d5430c9f05@infradead.org> (raw)
In-Reply-To: <1516157443-17716-4-git-send-email-sukadev@linux.vnet.ibm.com>
On 01/16/18 18:50, Sukadev Bhattiprolu wrote:
> The Fast Thread Wake-up (FTW) driver provides user space applications an
> interface to the low latency Core-to-Core wakeup functionality in POWER9.
>
> This mechanism allows a thread on one core to efficiently send a message
> to a "waiting thread" on another core on the same chip, using the Virtual
> Accelrator Switchboard (VAS) subsystem.
>
> This initial FTW driver implements the ioctl and mmap operations on an
> FTW device node. Using these operations, a pair of application threads
> can establish a "communication channel" and use the COPY, PASTE and WAIT
> instructions to wait/wake up.
>
> PATCH 5/5 documents the API and includes an example of the usage.
>
> Signed-off-by: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
> ---
> Changelog[v2]
> - [Michael Neuling] Rename from drop "nx" from name "nx-ftw".
> - [Michael Neuling] Use a single VAS_FTW_SETUP ioctl to simplify
> interface.
> - [Michael Ellerman] To work with paste emulation patch, mark
> PTE dirty in ->mmap() to ensure there is no fault on paste
> (the emulation patch must disable pagefaults when updating
> thread reconfig registers).
> - Check return value from set_thread_tidr().
> - Move driver drivers/misc/ftw.
>
> ---
> drivers/misc/Kconfig | 1 +
> drivers/misc/Makefile | 1 +
> drivers/misc/ftw/Kconfig | 16 +++
> drivers/misc/ftw/Makefile | 4 +
> drivers/misc/ftw/ftw.c | 346 ++++++++++++++++++++++++++++++++++++++++++++++
> 5 files changed, 368 insertions(+)
> create mode 100644 drivers/misc/ftw/Kconfig
> create mode 100644 drivers/misc/ftw/Makefile
> create mode 100644 drivers/misc/ftw/ftw.c
> +static long ftw_ioctl(struct file *fp, unsigned int cmd, unsigned long arg)
> +{
> + switch (cmd) {
> +
> + case FTW_SETUP:
> + return ftw_ioc_ftw_setup(fp, arg);
> +
> + default:
> + return -EINVAL;
> + }
> +}
Nit: some versions of gcc (or maybe clang) complain about a typed function
not always having a return value in code like above, so it is often done as:
> +static long ftw_ioctl(struct file *fp, unsigned int cmd, unsigned long arg)
> +{
> + switch (cmd) {
> +
> + case FTW_SETUP:
> + return ftw_ioc_ftw_setup(fp, arg);
> +
> + default:
> + break;
> + }
return -EINVAL;
> +}
Do you expect to implement more ioctls? If not, just change the switch to
an if ().
--
~Randy
next prev parent reply other threads:[~2018-01-17 18:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 2:50 [PATCH 0/5] Implement FTW driver Sukadev Bhattiprolu
2018-01-17 2:50 ` [PATCH 1/5] powerpc/vas: Remove a stray line in Makefile Sukadev Bhattiprolu
2018-03-14 9:27 ` [1/5] " Michael Ellerman
2018-01-17 2:50 ` [PATCH 2/5] powerpc/ftw: Define FTW_SETUP ioctl API Sukadev Bhattiprolu
2018-01-17 18:23 ` Randy Dunlap
2018-01-18 16:41 ` Sukadev Bhattiprolu
2018-01-17 2:50 ` [PATCH 3/5] powerpc/ftw: Implement a simple FTW driver Sukadev Bhattiprolu
2018-01-17 18:30 ` Randy Dunlap [this message]
2018-01-18 16:45 ` Sukadev Bhattiprolu
2018-01-17 2:50 ` [PATCH 4/5] powerpc/ftw: Add a couple of trace points Sukadev Bhattiprolu
2018-01-17 2:50 ` [PATCH 5/5] powerpc/ftw: Document FTW API/usage Sukadev Bhattiprolu
2018-01-25 0:48 ` Randy Dunlap
2018-01-25 3:05 ` Sukadev Bhattiprolu
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=e2d57c8c-9667-3b56-8d11-40d5430c9f05@infradead.org \
--to=rdunlap@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=hbabu@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mikey@neuling.org \
--cc=mpe@ellerman.id.au \
--cc=sukadev@linux.vnet.ibm.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).