From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: 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: [PATCH 0/5] Implement FTW driver
Date: Tue, 16 Jan 2018 18:50:38 -0800 [thread overview]
Message-ID: <1516157443-17716-1-git-send-email-sukadev@linux.vnet.ibm.com> (raw)
The Virtual Accelerator Switchboard (VAS) subsystem in the POWER9 processor
provides a low latency Core-to-core wakeup" mechanism which allows a thread
on one core the processor to efficiently send a message to a thread waiting
on another core.
This Fast thread-wakeup (FTW) driver provides user space applications an
interface to the Core-to-core wakeup mechanism. The FTW driver uses the
"external" interfaces provided by the VAS driver to interact with the VAS
hardware.
PATCH 5/5 documents the API.
The ftw-next branch on my github has some initial test cases for the
driver:
https://github.com/sukadev/linux/tree/ftw-next
Thanks to input from Ben Herrenschmidt, Michael Ellerman, Michael
Neuling and Robert Blackmore.
Sukadev Bhattiprolu (5):
powerpc/vas: Remove a stray line in Makefile
powerpc/ftw: Define FTW_SETUP ioctl API
powerpc/ftw: Implement a simple FTW driver
powerpc/ftw: Add a couple of trace points
powerpc/ftw: Document FTW API/usage
Documentation/powerpc/ftw-api.txt | 283 +++++++++++++++++++++++++
MAINTAINERS | 8 +
arch/powerpc/platforms/powernv/Makefile | 1 -
drivers/misc/Kconfig | 1 +
drivers/misc/Makefile | 1 +
drivers/misc/ftw/Kconfig | 16 ++
drivers/misc/ftw/Makefile | 4 +
drivers/misc/ftw/ftw-trace.h | 75 +++++++
drivers/misc/ftw/ftw.c | 352 ++++++++++++++++++++++++++++++++
include/uapi/misc/ftw.h | 31 +++
10 files changed, 771 insertions(+), 1 deletion(-)
create mode 100644 Documentation/powerpc/ftw-api.txt
create mode 100644 drivers/misc/ftw/Kconfig
create mode 100644 drivers/misc/ftw/Makefile
create mode 100644 drivers/misc/ftw/ftw-trace.h
create mode 100644 drivers/misc/ftw/ftw.c
create mode 100644 include/uapi/misc/ftw.h
--
2.7.4
next reply other threads:[~2018-01-17 2:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 2:50 Sukadev Bhattiprolu [this message]
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
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=1516157443-17716-1-git-send-email-sukadev@linux.vnet.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--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 \
/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).