2019-05-19 20:07:45 +08:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2014-10-08 16:55:01 +08:00
|
|
|
#
|
|
|
|
|
# IBM Coherent Accelerator (CXL) compatible devices
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
config CXL_BASE
|
|
|
|
|
bool
|
|
|
|
|
select PPC_COPRO_BASE
|
2014-10-08 16:55:04 +08:00
|
|
|
|
cxl: Add mechanism for delivering AFU driver specific events
This adds an afu_driver_ops structure with fetch_event() and
event_delivered() callbacks. An AFU driver such as cxlflash can fill
this out and associate it with a context to enable passing custom AFU
specific events to userspace.
This also adds a new kernel API function cxl_context_pending_events(),
that the AFU driver can use to notify the cxl driver that new specific
events are ready to be delivered, and wake up anyone waiting on the
context wait queue.
The current count of AFU driver specific events is stored in the field
afu_driver_events of the context structure.
The cxl driver checks the afu_driver_events count during poll, select,
read, etc. calls to check if an AFU driver specific event is pending,
and calls fetch_event() to obtain and deliver that event. This way, the
cxl driver takes care of all the usual locking semantics around these
calls and handles all the generic cxl events, so that the AFU driver
only needs to worry about it's own events.
fetch_event() return a struct cxl_event_afu_driver_reserved, allocated
by the AFU driver, and filled in with the specific event information and
size. Total event size (header + data) should not be greater than
CXL_READ_MIN_SIZE (4K).
Th cxl driver prepends an appropriate cxl event header, copies the event
to userspace, and finally calls event_delivered() to return the status of
the operation to the AFU driver. The event is identified by the context
and cxl_event_afu_driver_reserved pointers.
Since AFU drivers provide their own means for userspace to obtain the
AFU file descriptor (i.e. cxlflash uses an ioctl on their scsi file
descriptor to obtain the AFU file descriptor) and the generic cxl driver
will never use this event, the ABI of the event is up to each individual
AFU driver.
Signed-off-by: Philippe Bergheaud <felix@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
2016-06-23 21:03:53 +08:00
|
|
|
config CXL_AFU_DRIVER_OPS
|
|
|
|
|
bool
|
|
|
|
|
|
2017-06-22 21:07:27 +08:00
|
|
|
config CXL_LIB
|
|
|
|
|
bool
|
|
|
|
|
|
2014-10-08 16:55:04 +08:00
|
|
|
config CXL
|
|
|
|
|
tristate "Support for IBM Coherent Accelerators (CXL)"
|
2015-08-14 15:41:27 +08:00
|
|
|
depends on PPC_POWERNV && PCI_MSI && EEH
|
2014-10-08 16:55:04 +08:00
|
|
|
select CXL_BASE
|
cxl: Add mechanism for delivering AFU driver specific events
This adds an afu_driver_ops structure with fetch_event() and
event_delivered() callbacks. An AFU driver such as cxlflash can fill
this out and associate it with a context to enable passing custom AFU
specific events to userspace.
This also adds a new kernel API function cxl_context_pending_events(),
that the AFU driver can use to notify the cxl driver that new specific
events are ready to be delivered, and wake up anyone waiting on the
context wait queue.
The current count of AFU driver specific events is stored in the field
afu_driver_events of the context structure.
The cxl driver checks the afu_driver_events count during poll, select,
read, etc. calls to check if an AFU driver specific event is pending,
and calls fetch_event() to obtain and deliver that event. This way, the
cxl driver takes care of all the usual locking semantics around these
calls and handles all the generic cxl events, so that the AFU driver
only needs to worry about it's own events.
fetch_event() return a struct cxl_event_afu_driver_reserved, allocated
by the AFU driver, and filled in with the specific event information and
size. Total event size (header + data) should not be greater than
CXL_READ_MIN_SIZE (4K).
Th cxl driver prepends an appropriate cxl event header, copies the event
to userspace, and finally calls event_delivered() to return the status of
the operation to the AFU driver. The event is identified by the context
and cxl_event_afu_driver_reserved pointers.
Since AFU drivers provide their own means for userspace to obtain the
AFU file descriptor (i.e. cxlflash uses an ioctl on their scsi file
descriptor to obtain the AFU file descriptor) and the generic cxl driver
will never use this event, the ABI of the event is up to each individual
AFU driver.
Signed-off-by: Philippe Bergheaud <felix@linux.vnet.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
2016-06-23 21:03:53 +08:00
|
|
|
select CXL_AFU_DRIVER_OPS
|
2017-06-22 21:07:27 +08:00
|
|
|
select CXL_LIB
|
2014-10-08 16:55:04 +08:00
|
|
|
default m
|
|
|
|
|
help
|
|
|
|
|
Select this option to enable driver support for IBM Coherent
|
|
|
|
|
Accelerators (CXL). CXL is otherwise known as Coherent Accelerator
|
|
|
|
|
Processor Interface (CAPI). CAPI allows accelerators in FPGAs to be
|
|
|
|
|
coherently attached to a CPU via an MMU. This driver enables
|
|
|
|
|
userspace programs to access these accelerators via /dev/cxl/afuM.N
|
|
|
|
|
devices.
|
|
|
|
|
|
|
|
|
|
CAPI adapters are found in POWER8 based systems.
|
|
|
|
|
|
|
|
|
|
If unsure, say N.
|