Loading Documentation/ABI/stable/sysfs-driver-dma-idxd +9 −0 Original line number Original line Diff line number Diff line Loading @@ -128,6 +128,8 @@ Date: Aug 28, 2020 KernelVersion: 5.10.0 KernelVersion: 5.10.0 Contact: dmaengine@vger.kernel.org Contact: dmaengine@vger.kernel.org Description: The last executed device administrative command's status/error. Description: The last executed device administrative command's status/error. Also last configuration error overloaded. Writing to it will clear the status. What: /sys/bus/dsa/devices/wq<m>.<n>/block_on_fault What: /sys/bus/dsa/devices/wq<m>.<n>/block_on_fault Date: Oct 27, 2020 Date: Oct 27, 2020 Loading Loading @@ -211,6 +213,13 @@ Contact: dmaengine@vger.kernel.org Description: Indicate whether ATS disable is turned on for the workqueue. Description: Indicate whether ATS disable is turned on for the workqueue. 0 indicates ATS is on, and 1 indicates ATS is off for the workqueue. 0 indicates ATS is on, and 1 indicates ATS is off for the workqueue. What: /sys/bus/dsa/devices/wq<m>.<n>/occupancy Date May 25, 2021 KernelVersion: 5.14.0 Contact: dmaengine@vger.kernel.org Description: Show the current number of entries in this WQ if WQ Occupancy Support bit WQ capabilities is 1. What: /sys/bus/dsa/devices/engine<m>.<n>/group_id What: /sys/bus/dsa/devices/engine<m>.<n>/group_id Date: Oct 25, 2019 Date: Oct 25, 2019 KernelVersion: 5.6.0 KernelVersion: 5.6.0 Loading Documentation/ABI/testing/debugfs-driver-habanalabs +19 −0 Original line number Original line Diff line number Diff line Loading @@ -215,6 +215,17 @@ Description: Sets the skip reset on timeout option for the device. Value of "0" means device will be reset in case some CS has timed out, "0" means device will be reset in case some CS has timed out, otherwise it will not be reset. otherwise it will not be reset. What: /sys/kernel/debug/habanalabs/hl<n>/state_dump Date: Oct 2021 KernelVersion: 5.15 Contact: ynudelman@habana.ai Description: Gets the state dump occurring on a CS timeout or failure. State dump is used for debug and is created each time in case of a problem in a CS execution, before reset. Reading from the node returns the newest state dump available. Writing an integer X discards X state dumps, so that the next read would return X+1-st newest state dump. What: /sys/kernel/debug/habanalabs/hl<n>/stop_on_err What: /sys/kernel/debug/habanalabs/hl<n>/stop_on_err Date: Mar 2020 Date: Mar 2020 KernelVersion: 5.6 KernelVersion: 5.6 Loading @@ -230,6 +241,14 @@ Description: Displays a list with information about the currently user pointers (user virtual addresses) that are pinned and mapped pointers (user virtual addresses) that are pinned and mapped to DMA addresses to DMA addresses What: /sys/kernel/debug/habanalabs/hl<n>/userptr_lookup Date: Aug 2021 KernelVersion: 5.15 Contact: ogabbay@kernel.org Description: Allows to search for specific user pointers (user virtual addresses) that are pinned and mapped to DMA addresses, and see their resolution to the specific dma address. What: /sys/kernel/debug/habanalabs/hl<n>/vm What: /sys/kernel/debug/habanalabs/hl<n>/vm Date: Jan 2019 Date: Jan 2019 KernelVersion: 5.1 KernelVersion: 5.1 Loading Documentation/ABI/testing/sysfs-bus-pci +17 −0 Original line number Original line Diff line number Diff line Loading @@ -121,6 +121,23 @@ Description: child buses, and re-discover devices removed earlier child buses, and re-discover devices removed earlier from this part of the device tree. from this part of the device tree. What: /sys/bus/pci/devices/.../reset_method Date: August 2021 Contact: Amey Narkhede <ameynarkhede03@gmail.com> Description: Some devices allow an individual function to be reset without affecting other functions in the same slot. For devices that have this support, a file named reset_method is present in sysfs. Reading this file gives names of the supported and enabled reset methods and their ordering. Writing a space-separated list of names of reset methods sets the reset methods and ordering to be used when resetting the device. Writing an empty string disables the ability to reset the device. Writing "default" enables all supported reset methods in the default ordering. What: /sys/bus/pci/devices/.../reset What: /sys/bus/pci/devices/.../reset Date: July 2009 Date: July 2009 Contact: Michael S. Tsirkin <mst@redhat.com> Contact: Michael S. Tsirkin <mst@redhat.com> Loading Documentation/PCI/endpoint/pci-endpoint-cfs.rst +11 −1 Original line number Original line Diff line number Diff line Loading @@ -43,6 +43,7 @@ entries corresponding to EPF driver will be created by the EPF core. .. <EPF Driver1>/ .. <EPF Driver1>/ ... <EPF Device 11>/ ... <EPF Device 11>/ ... <EPF Device 21>/ ... <EPF Device 21>/ ... <EPF Device 31>/ .. <EPF Driver2>/ .. <EPF Driver2>/ ... <EPF Device 12>/ ... <EPF Device 12>/ ... <EPF Device 22>/ ... <EPF Device 22>/ Loading @@ -68,6 +69,7 @@ created) ... subsys_vendor_id ... subsys_vendor_id ... subsys_id ... subsys_id ... interrupt_pin ... interrupt_pin ... <Symlink EPF Device 31>/ ... primary/ ... primary/ ... <Symlink EPC Device1>/ ... <Symlink EPC Device1>/ ... secondary/ ... secondary/ Loading @@ -79,6 +81,13 @@ interface should be added in 'primary' directory and symlink of endpoint controller connected to secondary interface should be added in 'secondary' controller connected to secondary interface should be added in 'secondary' directory. directory. The <EPF Device> directory can have a list of symbolic links (<Symlink EPF Device 31>) to other <EPF Device>. These symbolic links should be created by the user to represent the virtual functions that are bound to the physical function. In the above directory structure <EPF Device 11> is a physical function and <EPF Device 31> is a virtual function. An EPF device once it's linked to another EPF device, cannot be linked to a EPC device. EPC Device EPC Device ========== ========== Loading @@ -98,7 +107,8 @@ entries corresponding to EPC device will be created by the EPC core. The <EPC Device> directory will have a list of symbolic links to The <EPC Device> directory will have a list of symbolic links to <EPF Device>. These symbolic links should be created by the user to <EPF Device>. These symbolic links should be created by the user to represent the functions present in the endpoint device. represent the functions present in the endpoint device. Only <EPF Device> that represents a physical function can be linked to a EPC device. The <EPC Device> directory will also have a *start* field. Once The <EPC Device> directory will also have a *start* field. Once "1" is written to this field, the endpoint device will be ready to "1" is written to this field, the endpoint device will be ready to Loading Documentation/admin-guide/README.rst +1 −1 Original line number Original line Diff line number Diff line Loading @@ -259,7 +259,7 @@ Configuring the kernel Compiling the kernel Compiling the kernel -------------------- -------------------- - Make sure you have at least gcc 4.9 available. - Make sure you have at least gcc 5.1 available. For more information, refer to :ref:`Documentation/process/changes.rst <changes>`. For more information, refer to :ref:`Documentation/process/changes.rst <changes>`. Please note that you can still run a.out user programs with this kernel. Please note that you can still run a.out user programs with this kernel. Loading Loading
Documentation/ABI/stable/sysfs-driver-dma-idxd +9 −0 Original line number Original line Diff line number Diff line Loading @@ -128,6 +128,8 @@ Date: Aug 28, 2020 KernelVersion: 5.10.0 KernelVersion: 5.10.0 Contact: dmaengine@vger.kernel.org Contact: dmaengine@vger.kernel.org Description: The last executed device administrative command's status/error. Description: The last executed device administrative command's status/error. Also last configuration error overloaded. Writing to it will clear the status. What: /sys/bus/dsa/devices/wq<m>.<n>/block_on_fault What: /sys/bus/dsa/devices/wq<m>.<n>/block_on_fault Date: Oct 27, 2020 Date: Oct 27, 2020 Loading Loading @@ -211,6 +213,13 @@ Contact: dmaengine@vger.kernel.org Description: Indicate whether ATS disable is turned on for the workqueue. Description: Indicate whether ATS disable is turned on for the workqueue. 0 indicates ATS is on, and 1 indicates ATS is off for the workqueue. 0 indicates ATS is on, and 1 indicates ATS is off for the workqueue. What: /sys/bus/dsa/devices/wq<m>.<n>/occupancy Date May 25, 2021 KernelVersion: 5.14.0 Contact: dmaengine@vger.kernel.org Description: Show the current number of entries in this WQ if WQ Occupancy Support bit WQ capabilities is 1. What: /sys/bus/dsa/devices/engine<m>.<n>/group_id What: /sys/bus/dsa/devices/engine<m>.<n>/group_id Date: Oct 25, 2019 Date: Oct 25, 2019 KernelVersion: 5.6.0 KernelVersion: 5.6.0 Loading
Documentation/ABI/testing/debugfs-driver-habanalabs +19 −0 Original line number Original line Diff line number Diff line Loading @@ -215,6 +215,17 @@ Description: Sets the skip reset on timeout option for the device. Value of "0" means device will be reset in case some CS has timed out, "0" means device will be reset in case some CS has timed out, otherwise it will not be reset. otherwise it will not be reset. What: /sys/kernel/debug/habanalabs/hl<n>/state_dump Date: Oct 2021 KernelVersion: 5.15 Contact: ynudelman@habana.ai Description: Gets the state dump occurring on a CS timeout or failure. State dump is used for debug and is created each time in case of a problem in a CS execution, before reset. Reading from the node returns the newest state dump available. Writing an integer X discards X state dumps, so that the next read would return X+1-st newest state dump. What: /sys/kernel/debug/habanalabs/hl<n>/stop_on_err What: /sys/kernel/debug/habanalabs/hl<n>/stop_on_err Date: Mar 2020 Date: Mar 2020 KernelVersion: 5.6 KernelVersion: 5.6 Loading @@ -230,6 +241,14 @@ Description: Displays a list with information about the currently user pointers (user virtual addresses) that are pinned and mapped pointers (user virtual addresses) that are pinned and mapped to DMA addresses to DMA addresses What: /sys/kernel/debug/habanalabs/hl<n>/userptr_lookup Date: Aug 2021 KernelVersion: 5.15 Contact: ogabbay@kernel.org Description: Allows to search for specific user pointers (user virtual addresses) that are pinned and mapped to DMA addresses, and see their resolution to the specific dma address. What: /sys/kernel/debug/habanalabs/hl<n>/vm What: /sys/kernel/debug/habanalabs/hl<n>/vm Date: Jan 2019 Date: Jan 2019 KernelVersion: 5.1 KernelVersion: 5.1 Loading
Documentation/ABI/testing/sysfs-bus-pci +17 −0 Original line number Original line Diff line number Diff line Loading @@ -121,6 +121,23 @@ Description: child buses, and re-discover devices removed earlier child buses, and re-discover devices removed earlier from this part of the device tree. from this part of the device tree. What: /sys/bus/pci/devices/.../reset_method Date: August 2021 Contact: Amey Narkhede <ameynarkhede03@gmail.com> Description: Some devices allow an individual function to be reset without affecting other functions in the same slot. For devices that have this support, a file named reset_method is present in sysfs. Reading this file gives names of the supported and enabled reset methods and their ordering. Writing a space-separated list of names of reset methods sets the reset methods and ordering to be used when resetting the device. Writing an empty string disables the ability to reset the device. Writing "default" enables all supported reset methods in the default ordering. What: /sys/bus/pci/devices/.../reset What: /sys/bus/pci/devices/.../reset Date: July 2009 Date: July 2009 Contact: Michael S. Tsirkin <mst@redhat.com> Contact: Michael S. Tsirkin <mst@redhat.com> Loading
Documentation/PCI/endpoint/pci-endpoint-cfs.rst +11 −1 Original line number Original line Diff line number Diff line Loading @@ -43,6 +43,7 @@ entries corresponding to EPF driver will be created by the EPF core. .. <EPF Driver1>/ .. <EPF Driver1>/ ... <EPF Device 11>/ ... <EPF Device 11>/ ... <EPF Device 21>/ ... <EPF Device 21>/ ... <EPF Device 31>/ .. <EPF Driver2>/ .. <EPF Driver2>/ ... <EPF Device 12>/ ... <EPF Device 12>/ ... <EPF Device 22>/ ... <EPF Device 22>/ Loading @@ -68,6 +69,7 @@ created) ... subsys_vendor_id ... subsys_vendor_id ... subsys_id ... subsys_id ... interrupt_pin ... interrupt_pin ... <Symlink EPF Device 31>/ ... primary/ ... primary/ ... <Symlink EPC Device1>/ ... <Symlink EPC Device1>/ ... secondary/ ... secondary/ Loading @@ -79,6 +81,13 @@ interface should be added in 'primary' directory and symlink of endpoint controller connected to secondary interface should be added in 'secondary' controller connected to secondary interface should be added in 'secondary' directory. directory. The <EPF Device> directory can have a list of symbolic links (<Symlink EPF Device 31>) to other <EPF Device>. These symbolic links should be created by the user to represent the virtual functions that are bound to the physical function. In the above directory structure <EPF Device 11> is a physical function and <EPF Device 31> is a virtual function. An EPF device once it's linked to another EPF device, cannot be linked to a EPC device. EPC Device EPC Device ========== ========== Loading @@ -98,7 +107,8 @@ entries corresponding to EPC device will be created by the EPC core. The <EPC Device> directory will have a list of symbolic links to The <EPC Device> directory will have a list of symbolic links to <EPF Device>. These symbolic links should be created by the user to <EPF Device>. These symbolic links should be created by the user to represent the functions present in the endpoint device. represent the functions present in the endpoint device. Only <EPF Device> that represents a physical function can be linked to a EPC device. The <EPC Device> directory will also have a *start* field. Once The <EPC Device> directory will also have a *start* field. Once "1" is written to this field, the endpoint device will be ready to "1" is written to this field, the endpoint device will be ready to Loading
Documentation/admin-guide/README.rst +1 −1 Original line number Original line Diff line number Diff line Loading @@ -259,7 +259,7 @@ Configuring the kernel Compiling the kernel Compiling the kernel -------------------- -------------------- - Make sure you have at least gcc 4.9 available. - Make sure you have at least gcc 5.1 available. For more information, refer to :ref:`Documentation/process/changes.rst <changes>`. For more information, refer to :ref:`Documentation/process/changes.rst <changes>`. Please note that you can still run a.out user programs with this kernel. Please note that you can still run a.out user programs with this kernel. Loading
Jakub Kicinski <kuba@kernel.org>Jakub Kicinski <kuba@kernel.org>