€•¯V      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ3/translations/zh_CN/userspace-api/accelerators/ocxl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ3/translations/zh_TW/userspace-api/accelerators/ocxl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ3/translations/it_IT/userspace-api/accelerators/ocxl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ3/translations/ja_JP/userspace-api/accelerators/ocxl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ3/translations/ko_KR/userspace-api/accelerators/ocxl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ3/translations/sp_SP/userspace-api/accelerators/ocxl”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ8OpenCAPI (Open Coherent Accelerator Processor Interface)”h]”hŒ8OpenCAPI (Open Coherent Accelerator Processor Interface)”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒM/var/lib/git/docbuild/linux/Documentation/userspace-api/accelerators/ocxl.rst”h KubhŒ	paragraph”“”)”}”(hŒnOpenCAPI is an interface between processors and accelerators. It aims
at being low-latency and high-bandwidth.”h]”hŒnOpenCAPI is an interface between processors and accelerators. It aims
at being low-latency and high-bandwidth.”…””}”(hh¹hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒÇThe specification was developed by the OpenCAPI Consortium, and is now
available from the `Compute Express Link Consortium
<https://computeexpresslink.org/resource/opencapi-specification-archive/>`_.”h]”(hŒZThe specification was developed by the OpenCAPI Consortium, and is now
available from the ”…””}”(hhÇhžhhŸNh NubhŒ	reference”“”)”}”(hŒl`Compute Express Link Consortium
<https://computeexpresslink.org/resource/opencapi-specification-archive/>`_”h]”hŒCompute Express Link Consortium”…””}”(hhÑhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œname”ŒCompute Express Link Consortium”Œrefuri”ŒGhttps://computeexpresslink.org/resource/opencapi-specification-archive/”uh1hÏhhÇubhŒtarget”“”)”}”(hŒJ
<https://computeexpresslink.org/resource/opencapi-specification-archive/>”h]”h}”(h]”Œcompute-express-link-consortium”ah ]”h"]”Œcompute express link consortium”ah$]”h&]”Œrefuri”hâuh1hãŒ
referenced”KhhÇubhŒ.”…””}”(hhÇhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒÑIt allows an accelerator (which could be an FPGA, ASICs, ...) to access
the host memory coherently, using virtual addresses. An OpenCAPI
device can also host its own memory, that can be accessed from the
host.”h]”hŒÑIt allows an accelerator (which could be an FPGA, ASICs, ...) to access
the host memory coherently, using virtual addresses. An OpenCAPI
device can also host its own memory, that can be accessed from the
host.”…””}”(hhýhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¸)”}”(hŒ×OpenCAPI is known in linux as 'ocxl', as the open, processor-agnostic
evolution of 'cxl' (the driver for the IBM CAPI interface for
powerpc), which was named that way to avoid confusion with the ISDN
CAPI subsystem.”h]”hŒßOpenCAPI is known in linux as â€˜ocxlâ€™, as the open, processor-agnostic
evolution of â€˜cxlâ€™ (the driver for the IBM CAPI interface for
powerpc), which was named that way to avoid confusion with the ISDN
CAPI subsystem.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒHigh-level view”h]”hŒHigh-level view”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h Kubh¸)”}”(hŒ½OpenCAPI defines a Data Link Layer (DL) and Transaction Layer (TL), to
be implemented on top of a physical link. Any processor or device
implementing the DL and TL can start sharing memory.”h]”hŒ½OpenCAPI defines a Data Link Layer (DL) and Transaction Layer (TL), to
be implemented on top of a physical link. Any processor or device
implementing the DL and TL can start sharing memory.”…””}”(hj*  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khj  hžhubhŒliteral_block”“”)”}”(hX  +-----------+                         +-------------+
|           |                         |             |
|           |                         | Accelerated |
| Processor |                         |  Function   |
|           |  +--------+             |    Unit     |  +--------+
|           |--| Memory |             |    (AFU)    |--| Memory |
|           |  +--------+             |             |  +--------+
+-----------+                         +-------------+
     |                                       |
+-----------+                         +-------------+
|    TL     |                         |    TLX      |
+-----------+                         +-------------+
     |                                       |
+-----------+                         +-------------+
|    DL     |                         |    DLX      |
+-----------+                         +-------------+
     |                                       |
     |                   PHY                 |
     +---------------------------------------+”h]”hX  +-----------+                         +-------------+
|           |                         |             |
|           |                         | Accelerated |
| Processor |                         |  Function   |
|           |  +--------+             |    Unit     |  +--------+
|           |--| Memory |             |    (AFU)    |--| Memory |
|           |  +--------+             |             |  +--------+
+-----------+                         +-------------+
     |                                       |
+-----------+                         +-------------+
|    TL     |                         |    TLX      |
+-----------+                         +-------------+
     |                                       |
+-----------+                         +-------------+
|    DL     |                         |    DLX      |
+-----------+                         +-------------+
     |                                       |
     |                   PHY                 |
     +---------------------------------------+”…””}”hj:  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j8  hŸh¶h K hj  hžhubeh}”(h]”Œhigh-level-view”ah ]”h"]”Œhigh-level view”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒDevice discovery”h]”hŒDevice discovery”…””}”(hjU  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjR  hžhhŸh¶h K7ubh¸)”}”(hŒ‰OpenCAPI relies on a PCI-like configuration space, implemented on the
device. So the host can discover AFUs by querying the config space.”h]”hŒ‰OpenCAPI relies on a PCI-like configuration space, implemented on the
device. So the host can discover AFUs by querying the config space.”…””}”(hjc  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K9hjR  hžhubh¸)”}”(hXi  OpenCAPI devices in Linux are treated like PCI devices (with a few
caveats). The firmware is expected to abstract the hardware as if it
was a PCI link. A lot of the existing PCI infrastructure is reused:
devices are scanned and BARs are assigned during the standard PCI
enumeration. Commands like 'lspci' can therefore be used to see what
devices are available.”h]”hXm  OpenCAPI devices in Linux are treated like PCI devices (with a few
caveats). The firmware is expected to abstract the hardware as if it
was a PCI link. A lot of the existing PCI infrastructure is reused:
devices are scanned and BARs are assigned during the standard PCI
enumeration. Commands like â€˜lspciâ€™ can therefore be used to see what
devices are available.”…””}”(hjq  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K<hjR  hžhubh¸)”}”(hŒ²The configuration space defines the AFU(s) that can be found on the
physical adapter, such as its name, how many memory contexts it can
work with, the size of its MMIO areas, ...”h]”hŒ²The configuration space defines the AFU(s) that can be found on the
physical adapter, such as its name, how many memory contexts it can
work with, the size of its MMIO areas, ...”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KChjR  hžhubeh}”(h]”Œdevice-discovery”ah ]”h"]”Œdevice discovery”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K7ubh¢)”}”(hhh]”(h§)”}”(hŒMMIO”h]”hŒMMIO”…””}”(hj˜  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj•  hžhhŸh¶h KJubh¸)”}”(hŒ-OpenCAPI defines two MMIO areas for each AFU:”h]”hŒ-OpenCAPI defines two MMIO areas for each AFU:”…””}”(hj¦  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KLhj•  hžhubhŒbullet_list”“”)”}”(hhh]”(hŒ	list_item”“”)”}”(hŒ@the global MMIO area, with registers pertinent to the whole AFU.”h]”h¸)”}”(hj½  h]”hŒ@the global MMIO area, with registers pertinent to the whole AFU.”…””}”(hj¿  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KNhj»  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¹  hj¶  hžhhŸh¶h Nubjº  )”}”(hŒDa per-process MMIO area, which has a fixed size for each context.


”h]”h¸)”}”(hŒAa per-process MMIO area, which has a fixed size for each context.”h]”hŒAa per-process MMIO area, which has a fixed size for each context.”…””}”(hjÖ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KOhjÒ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¹  hj¶  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ*”uh1j´  hŸh¶h KNhj•  hžhubeh}”(h]”Œmmio”ah ]”h"]”Œmmio”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KJubh¢)”}”(hhh]”(h§)”}”(hŒAFU interrupts”h]”hŒAFU interrupts”…””}”(hjý  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjú  hžhhŸh¶h KTubh¸)”}”(hŒÖOpenCAPI includes the possibility for an AFU to send an interrupt to a
host process. It is done through a 'intrp_req' defined in the
Transaction Layer, specifying a 64-bit object handle which defines the
interrupt.”h]”hŒÚOpenCAPI includes the possibility for an AFU to send an interrupt to a
host process. It is done through a â€˜intrp_reqâ€™ defined in the
Transaction Layer, specifying a 64-bit object handle which defines the
interrupt.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KVhjú  hžhubh¸)”}”(hŒxThe driver allows a process to allocate an interrupt and obtain its
64-bit object handle, that can be passed to the AFU.”h]”hŒxThe driver allows a process to allocate an interrupt and obtain its
64-bit object handle, that can be passed to the AFU.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K[hjú  hžhubeh}”(h]”Œafu-interrupts”ah ]”h"]”Œafu interrupts”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KTubh¢)”}”(hhh]”(h§)”}”(hŒchar devices”h]”hŒchar devices”…””}”(hj2  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj/  hžhhŸh¶h Kaubh¸)”}”(hX  The driver creates one char device per AFU found on the physical
device. A physical device may have multiple functions and each
function can have multiple AFUs. At the time of this writing though,
it has only been tested with devices exporting only one AFU.”h]”hX  The driver creates one char device per AFU found on the physical
device. A physical device may have multiple functions and each
function can have multiple AFUs. At the time of this writing though,
it has only been tested with devices exporting only one AFU.”…””}”(hj@  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kchj/  hžhubh¸)”}”(hŒaChar devices can be found in /dev/ocxl/ and are named as:
/dev/ocxl/<AFU name>.<location>.<index>”h]”hŒaChar devices can be found in /dev/ocxl/ and are named as:
/dev/ocxl/<AFU name>.<location>.<index>”…””}”(hjN  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khhj/  hžhubh¸)”}”(hXY  where <AFU name> is a max 20-character long name, as found in the
config space of the AFU.
<location> is added by the driver and can help distinguish devices
when a system has more than one instance of the same OpenCAPI device.
<index> is also to help distinguish AFUs in the unlikely case where a
device carries multiple copies of the same AFU.”h]”hXY  where <AFU name> is a max 20-character long name, as found in the
config space of the AFU.
<location> is added by the driver and can help distinguish devices
when a system has more than one instance of the same OpenCAPI device.
<index> is also to help distinguish AFUs in the unlikely case where a
device carries multiple copies of the same AFU.”…””}”(hj\  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kkhj/  hžhubeh}”(h]”Œchar-devices”ah ]”h"]”Œchar devices”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kaubh¢)”}”(hhh]”(h§)”}”(hŒSysfs class”h]”hŒSysfs class”…””}”(hju  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjr  hžhhŸh¶h Kuubh¸)”}”(hŒ˜An ocxl class is added for the devices representing the AFUs. See
/sys/class/ocxl. The layout is described in
Documentation/ABI/testing/sysfs-class-ocxl”h]”hŒ˜An ocxl class is added for the devices representing the AFUs. See
/sys/class/ocxl. The layout is described in
Documentation/ABI/testing/sysfs-class-ocxl”…””}”(hjƒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kwhjr  hžhubeh}”(h]”Œsysfs-class”ah ]”h"]”Œsysfs class”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kuubh¢)”}”(hhh]”(h§)”}”(hŒUser API”h]”hŒUser API”…””}”(hjœ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj™  hžhhŸh¶h K~ubh¢)”}”(hhh]”(h§)”}”(hŒopen”h]”hŒopen”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjª  hžhhŸh¶h Kubh¸)”}”(hŒÒBased on the AFU definition found in the config space, an AFU may
support working with more than one memory context, in which case the
associated char device may be opened multiple times by different
processes.”h]”hŒÒBased on the AFU definition found in the config space, an AFU may
support working with more than one memory context, in which case the
associated char device may be opened multiple times by different
processes.”…””}”(hj»  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Kƒhjª  hžhubeh}”(h]”Œopen”ah ]”h"]”Œopen”ah$]”h&]”uh1h¡hj™  hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒioctl”h]”hŒioctl”…””}”(hjÔ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjÑ  hžhhŸh¶h KŠubh¸)”}”(hŒOCXL_IOCTL_ATTACH:”h]”hŒOCXL_IOCTL_ATTACH:”…””}”(hjâ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KŒhjÑ  hžhubhŒblock_quote”“”)”}”(hŒcAttach the memory context of the calling process to the AFU so that
the AFU can access its memory.
”h]”h¸)”}”(hŒbAttach the memory context of the calling process to the AFU so that
the AFU can access its memory.”h]”hŒbAttach the memory context of the calling process to the AFU so that
the AFU can access its memory.”…””}”(hjö  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KŽhjò  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jð  hŸh¶h KŽhjÑ  hžhubh¸)”}”(hŒOCXL_IOCTL_IRQ_ALLOC:”h]”hŒOCXL_IOCTL_IRQ_ALLOC:”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K‘hjÑ  hžhubjñ  )”}”(hŒ4Allocate an AFU interrupt and return an identifier.
”h]”h¸)”}”(hŒ3Allocate an AFU interrupt and return an identifier.”h]”hŒ3Allocate an AFU interrupt and return an identifier.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K“hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jð  hŸh¶h K“hjÑ  hžhubh¸)”}”(hŒOCXL_IOCTL_IRQ_FREE:”h]”hŒOCXL_IOCTL_IRQ_FREE:”…””}”(hj0  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K•hjÑ  hžhubjñ  )”}”(hŒ+Free a previously allocated AFU interrupt.
”h]”h¸)”}”(hŒ*Free a previously allocated AFU interrupt.”h]”hŒ*Free a previously allocated AFU interrupt.”…””}”(hjB  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K—hj>  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jð  hŸh¶h K—hjÑ  hžhubh¸)”}”(hŒOCXL_IOCTL_IRQ_SET_FD:”h]”hŒOCXL_IOCTL_IRQ_SET_FD:”…””}”(hjV  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K™hjÑ  hžhubjñ  )”}”(hŒtAssociate an event fd to an AFU interrupt so that the user process
can be notified when the AFU sends an interrupt.
”h]”h¸)”}”(hŒsAssociate an event fd to an AFU interrupt so that the user process
can be notified when the AFU sends an interrupt.”h]”hŒsAssociate an event fd to an AFU interrupt so that the user process
can be notified when the AFU sends an interrupt.”…””}”(hjh  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K›hjd  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jð  hŸh¶h K›hjÑ  hžhubh¸)”}”(hŒOCXL_IOCTL_GET_METADATA:”h]”hŒOCXL_IOCTL_GET_METADATA:”…””}”(hj|  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h KžhjÑ  hžhubjñ  )”}”(hŒ‰Obtains configuration information from the card, such at the size of
MMIO areas, the AFU version, and the PASID for the current context.
”h]”h¸)”}”(hŒˆObtains configuration information from the card, such at the size of
MMIO areas, the AFU version, and the PASID for the current context.”h]”hŒˆObtains configuration information from the card, such at the size of
MMIO areas, the AFU version, and the PASID for the current context.”…””}”(hjŽ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K hjŠ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jð  hŸh¶h K hjÑ  hžhubh¸)”}”(hŒOCXL_IOCTL_ENABLE_P9_WAIT:”h]”hŒOCXL_IOCTL_ENABLE_P9_WAIT:”…””}”(hj¢  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K£hjÑ  hžhubjñ  )”}”(hŒ«Allows the AFU to wake a userspace thread executing 'wait'. Returns
information to userspace to allow it to configure the AFU. Note that
this is only available on POWER9.
”h]”h¸)”}”(hŒªAllows the AFU to wake a userspace thread executing 'wait'. Returns
information to userspace to allow it to configure the AFU. Note that
this is only available on POWER9.”h]”hŒ®Allows the AFU to wake a userspace thread executing â€˜waitâ€™. Returns
information to userspace to allow it to configure the AFU. Note that
this is only available on POWER9.”…””}”(hj´  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K¥hj°  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jð  hŸh¶h K¥hjÑ  hžhubh¸)”}”(hŒOCXL_IOCTL_GET_FEATURES:”h]”hŒOCXL_IOCTL_GET_FEATURES:”…””}”(hjÈ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K©hjÑ  hžhubjñ  )”}”(hŒOReports on which CPU features that affect OpenCAPI are usable from
userspace.

”h]”h¸)”}”(hŒMReports on which CPU features that affect OpenCAPI are usable from
userspace.”h]”hŒMReports on which CPU features that affect OpenCAPI are usable from
userspace.”…””}”(hjÚ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K«hjÖ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jð  hŸh¶h K«hjÑ  hžhubeh}”(h]”Œioctl”ah ]”h"]”Œioctl”ah$]”h&]”uh1h¡hj™  hžhhŸh¶h KŠubh¢)”}”(hhh]”(h§)”}”(hŒmmap”h]”hŒmmap”…””}”(hjù  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjö  hžhhŸh¶h K°ubh¸)”}”(hŒKA process can mmap the per-process MMIO area for interactions with the
AFU.”h]”hŒKA process can mmap the per-process MMIO area for interactions with the
AFU.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h K²hjö  hžhubeh}”(h]”Œmmap”ah ]”h"]”Œmmap”ah$]”h&]”uh1h¡hj™  hžhhŸh¶h K°ubeh}”(h]”Œuser-api”ah ]”h"]”Œuser api”ah$]”h&]”uh1h¡hh£hžhhŸh¶h K~ubeh}”(h]”Œ6opencapi-open-coherent-accelerator-processor-interface”ah ]”h"]”Œ8opencapi (open coherent accelerator processor interface)”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jP  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œrefids”}”Œnameids”}”(j*  j'  hîhëjO  jL  j’  j  j÷  jô  j,  j)  jo  jl  j–  j“  j"  j  jÎ  jË  jó  jð  j  j  uŒ	nametypes”}”(j*  ‰hîˆjO  ‰j’  ‰j÷  ‰j,  ‰jo  ‰j–  ‰j"  ‰jÎ  ‰jó  ‰j  ‰uh}”(j'  h£hëhåjL  j  j  jR  jô  j•  j)  jú  jl  j/  j“  jr  j  j™  jË  jª  jð  jÑ  j  jö  uŒfootnote_refs”}”Œcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”Œ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”…”R”Œparse_messages”]”Œtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.