Changes in Makefile

ceb8bf2c - module: Convert default symbol namespace to string literal

Tue, 03 Dec 2024 10:21:07 +0000

module: Convert default symbol namespace to string literalCommit cdd30ebb1b9f ("module: Convert symbol namespace to stringliteral") only converted MODULE_IMPORT_NS() and EXPORT_SYMBOL_NS(),leaving DEFAULT_SYMBOL_NAMESPACE as a macro expansion.This commit converts DEFAULT_SYMBOL_NAMESPACE in the same way to avoidannoyance for the default namespace as well.Signed-off-by: Masahiro Yamada Reviewed-by: Uwe Kleine-König Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/dma/idxd/Makefile

979f6ded - dmaengine: idxd: Add support for device/wq defaults

Tue, 05 Dec 2023 21:25:30 +0000

dmaengine: idxd: Add support for device/wq defaultsAdd a load_device_defaults() function pointer to structidxd_driver_data, which if defined, will be called when an idxd deviceis probed and will allow the idxd device to be configured with defaultvalues.The load_device_defaults() function is passed an idxd device to workwith to set specific device attributes.Also add a load_device_defaults() implementation IAA devices; futurepatches would add default functions for other device types such asDSA.The way idxd device probing works, if the device configuration isvalid at that point e.g. at least one workqueue and engine is properlyconfigured then the device will be enabled and ready to go.The IAA implementation, idxd_load_iaa_device_defaults(), configures asingle workqueue (wq0) for each device with the following defaultvalues: mode "dedicated" threshold 0 size Total WQ Size from WQCAP priority 10 type IDXD_WQT_KERNEL group 0 name "iaa_crypto" driver_name "crypto"Note that this now adds another configuration step for any users thatwant to configure their own devices/workqueus with something differentin that they'll first need to disable (in the case of IAA) wq0 and thedevice itself before they can set their own attributes and re-enable,since they've been already been auto-enabled. Note also that in orderfor the new configuration to be applied to the deflate-iaa cryptoalgorithm the iaa_crypto module needs to unregister the old version,which is accomplished by removing the iaa_crypto module, andre-registering it with the new configuration by reinserting theiaa_crypto module.Signed-off-by: Tom Zanussi Reviewed-by: Dave Jiang Signed-off-by: Herbert Xu List of files: /linux-6.15/drivers/dma/idxd/Makefile

88928add - dmaengine: idxd: Register dsa_bus_type before registering idxd sub-drivers

Sun, 24 Sep 2023 16:22:32 +0000

dmaengine: idxd: Register dsa_bus_type before registering idxd sub-driversidxd sub-drivers belong to bus dsa_bus_type. Thus, dsa_bus_type must beregistered in dsa bus init before idxd drivers can be registered.But the order is wrong when both idxd and idxd_bus are builtin drivers.In this case, idxd driver is compiled and linked before idxd_bus driver.Since the initcall order is determined by the link order, idxd sub-driversare registered in idxd initcall before dsa_bus_type is registeredin idxd_bus initcall. idxd initcall fails:[ 21.562803] calling idxd_init_module+0x0/0x110 @ 1[ 21.570761] Driver 'idxd' was unable to register with bus_type 'dsa' because the bus was not initialized.[ 21.586475] initcall idxd_init_module+0x0/0x110 returned -22 after 15717 usecs[ 21.597178] calling dsa_bus_init+0x0/0x20 @ 1To fix the issue, compile and link idxd_bus driver before idxd driverto ensure the right registration order.Fixes: d9e5481fca74 ("dmaengine: dsa: move dsa_bus_type out of idxd driver to standalone")Reported-by: Michael Prinke Signed-off-by: Fenghua Yu Reviewed-by: Dave Jiang Reviewed-by: Lijun Pan Tested-by: Lijun Pan Link: https://lore.kernel.org/r/20230924162232.1409454-1-fenghua.yu@intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

5fbe6503 - dmanegine: idxd: add debugfs for event log dump

Fri, 07 Apr 2023 20:31:32 +0000

dmanegine: idxd: add debugfs for event log dumpAdd debugfs entry to dump the content of the event log for debugging. Thefunction will dump all non-zero entries in the event log. It will notewhich entries are processed and which entries are still pending processingat the time of the dump. The entries may not always be in chronologicalorder due to the log is a circular buffer.Tested-by: Tony Zhu Signed-off-by: Dave Jiang Co-developed-by: Fenghua Yu Signed-off-by: Fenghua Yu Link: https://lore.kernel.org/r/20230407203143.2189681-6-fenghua.yu@intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

6e7f3ee9 - dmaengine: idxd: move dsa_drv support to compatible mode

Thu, 15 Jul 2021 18:44:47 +0000

dmaengine: idxd: move dsa_drv support to compatible modeThe original architecture of /sys/bus/dsa invented a scheme wherebya single entry in the list of bus drivers, /sys/bus/drivers/dsa,handled all device types and internally routed them to differentdifferent drivers. Those internal drivers were invisible touserspace.With the idxd driver transitioned to a proper bus device-driver model,the legacy behavior needs to be preserved due to it being exposed touser space via sysfs. Create a compat driver to provide the legacybehavior for /sys/bus/dsa/drivers/dsa. This should satisfy usertool accel-config v3.2 or ealier where this behavior is expected.If the distro has a newer accel-config then the legacy mode doesnot need to be enabled.When the compat driver binds the device (i.e. dsa0) to the dsa driver,it will be bound to the new idxd_drv. The wq device (i.e. wq0.0) willbe bound to either the dmaengine_drv or the user_drv. The dsa_drvbecomes a routing mechansim for the new drivers. It will not supportadditional external drivers that are implemented later.Reviewed-by: Dan Williams Signed-off-by: Dave Jiang Link: https://lore.kernel.org/r/162637468705.744545.4399080971745974435.stgit@djiang5-desk3.ch.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

d9e5481f - dmaengine: dsa: move dsa_bus_type out of idxd driver to standalone

Thu, 15 Jul 2021 18:44:41 +0000

dmaengine: dsa: move dsa_bus_type out of idxd driver to standaloneIn preparation for dsa_drv compat support to be built-in, move the buscode to its own compilation unit. A follow-on patch adds the compatimplementation. Recall that the compat implementation allows for thedeprecated / omnibus dsa_drv binding scheme rather than the idiomaticorganization of a full fledged bus driver per driver type.Reviewed-by: Dan Williams Signed-off-by: Dave Jiang Link: https://lore.kernel.org/r/162637468142.744545.2811632736881720857.stgit@djiang5-desk3.ch.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

81dd4d4d - dmaengine: idxd: Add IDXD performance monitor support

Sat, 24 Apr 2021 15:04:15 +0000

dmaengine: idxd: Add IDXD performance monitor supportImplement the IDXD performance monitor capability (named 'perfmon' inthe DSA (Data Streaming Accelerator) spec [1]), which supports thecollection of information about key events occurring during DSA andIAX (Intel Analytics Accelerator) device execution, to assist inperformance tuning and debugging.The idxd perfmon support is implemented as part of the IDXD driver andinterfaces with the Linux perf framework. It has several features incommon with the existing uncore pmu support: - it does not support sampling - does not support per-thread countingHowever it also has some unique features not present in the core anduncore support: - all general-purpose counters are identical, thus no event constraints - operation is always system-wideWhile the core perf subsystem assumes that all counters are by defaultper-cpu, the uncore pmus are socket-scoped and use a cpu mask torestrict counting to one cpu from each socket. IDXD counters use asimilar strategy but expand the scope even further; since IDXDcounters are system-wide and can be read from any cpu, the IDXD perfdriver picks a single cpu to do the work (with cpu hotplug notifiersto choose a different cpu if the chosen one is taken off-line).More specifically, the perf userspace tool by default opens a counterfor each cpu for an event. However, if it finds a cpumask fileassociated with the pmu under sysfs, as is the case with the uncorepmus, it will open counters only on the cpus specified by the cpumask.Since perfmon only needs to open a single counter per event for agiven IDXD device, the perfmon driver will create a sysfs cpumask filefor the device and insert the first cpu of the system into it. When auser uses perf to open an event, perf will open a single counter onthe cpu specified by the cpu mask. This amounts to the defaultsystem-wide rather than per-cpu counting mentioned previously forperfmon pmu events. In order to keep the cpu mask up-to-date, thedriver implements cpu hotplug support for multiple devices, as IDXDusually enumerates and registers more than one idxd device.The perfmon driver implements basic perfmon hardware capabilitydiscovery and configuration, and is initialized by the IDXD driver'sprobe function. During initialization, the driver retrieves the totalnumber of supported performance counters, the pmu ID, and the devicetype from idxd device, and registers itself under the Linux perfframework.The perf userspace tool can be used to monitor single or multipleevents depending on the given configuration, as well as event groups,which are also supported by the perfmon driver. The user configuresevents using the perf tool command-line interface by specifying theevent and corresponding event category, along with an optional set offilters that can be used to restrict counting to specific work queues,traffic classes, page and transfer sizes, and engines (See [1] forspecifics).With the configuration specified by the user, the perf tool issues asystem call passing that information to the kernel, which uses it toinitialize the specified event(s). The event(s) are opened andstarted, and following termination of the perf command, they'restopped. At that point, the perfmon driver will read the latest countfor the event(s), calculate the difference between the latest countervalues and previously tracked counter values, and display the finalincremental count as the event count for the cycle. An overflowhandler registered on the IDXD irq path is used to account for counteroverflows, which are signaled by an overflow interrupt.Below are a couple of examples of perf usage for monitoring DSA events.The following monitors all events in the 'engine' category. Becuuseno filters are specified, this captures all engine events for theworkload, which in this case is 19 iterations of the work generated bythe kernel dmatest module.Details describing the events can be found in Appendix D of [1],Performance Monitoring Events, but briefly they are: event 0x1: total input data processed, in 32-byte units event 0x2: total data written, in 32-byte units event 0x4: number of work descriptors that read the source event 0x8: number of work descriptors that write the destination event 0x10: number of work descriptors dispatched from batch descriptors event 0x20: number of work descriptors dispatched from work queues # perf stat -e dsa0/event=0x1,event_category=0x1/, dsa0/event=0x2,event_category=0x1/, dsa0/event=0x4,event_category=0x1/, dsa0/event=0x8,event_category=0x1/, dsa0/event=0x10,event_category=0x1/, dsa0/event=0x20,event_category=0x1/ modprobe dmatest channel=dma0chan0 timeout=2000 iterations=19 run=1 wait=1 Performance counter stats for 'system wide': 5,332 dsa0/event=0x1,event_category=0x1/ 5,327 dsa0/event=0x2,event_category=0x1/ 19 dsa0/event=0x4,event_category=0x1/ 19 dsa0/event=0x8,event_category=0x1/ 0 dsa0/event=0x10,event_category=0x1/ 19 dsa0/event=0x20,event_category=0x1/ 21.977436186 seconds time elapsedThe command below illustrates filter usage with a simple example. Itspecifies that MEM_MOVE operations should be counted for the DSAdevice dsa0 (event 0x8 corresponds to the EV_MEM_MOVE event - Numberof Memory Move Descriptors, which is part of event category 0x3 -Operations. The detailed category and event IDs are available inAppendix D, Performance Monitoring Events, of [1]). In addition tothe event and event category, a number of filters are also specified(the detailed filter values are available in Chapter 6.4 (FilterSupport) of [1]), which will restrict counting to only those eventsthat meet all of the filter criteria. In this case, the filtersspecify that only MEM_MOVE operations that are serviced by work queuewq0 and specifically engine number engine0 and traffic class tc0having sizes between 0 and 4k and page size of between 0 and 1G resultin a counter hit; anything else will be filtered out and not appear inthe final count. Note that filters are optional - any filter notspecified is assumed to be all ones and will pass anything. # perf stat -e dsa0/filter_wq=0x1,filter_tc=0x1,filter_sz=0x7, filter_eng=0x1,event=0x8,event_category=0x3/ modprobe dmatest channel=dma0chan0 timeout=2000 iterations=19 run=1 wait=1 Performance counter stats for 'system wide': 19 dsa0/filter_wq=0x1,filter_tc=0x1,filter_sz=0x7, filter_eng=0x1,event=0x8,event_category=0x3/ 21.865914091 seconds time elapsedThe output above reflects that the unspecified workload resulted inthe counting of 19 MEM_MOVE operation events that met the filtercriteria.[1]: https://software.intel.com/content/www/us/en/develop/download/intel-data-streaming-accelerator-preliminary-architecture-specification.html[ Based on work originally by Jing Lin. ]Reviewed-by: Dave Jiang Reviewed-by: Kan Liang Signed-off-by: Tom Zanussi Link: https://lore.kernel.org/r/0c5080a7d541904c4ad42b848c76a1ce056ddac7.1619276133.git.zanussi@kernel.orgSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

42d279f9 - dmaengine: idxd: add char driver to expose submission portal to userland

Tue, 21 Jan 2020 23:44:29 +0000

dmaengine: idxd: add char driver to expose submission portal to userlandCreate a char device region that will allow acquisition of user portals inorder to allow applications to submit DMA operations. A char device will becreated per work queue that gets exposed. The workqueue type "user"is used to mark a work queue for user char device. For example if theworkqueue 0 of DSA device 0 is marked for char device, then a device nodeof /dev/dsa/wq0.0 will be created.Signed-off-by: Dave Jiang Link: https://lore.kernel.org/r/157965026985.73301.976523230037106742.stgit@djiang5-desk3.ch.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

8f47d1a5 - dmaengine: idxd: connect idxd to dmaengine subsystem

Tue, 21 Jan 2020 23:44:23 +0000

dmaengine: idxd: connect idxd to dmaengine subsystemAdd plumbing for dmaengine subsystem connection. The driver register a DMAdevice per DSA device. The channels are dynamically registered when aworkqueue is configured to be "kernel:dmanegine" type.Signed-off-by: Dave Jiang Link: https://lore.kernel.org/r/157965026376.73301.13867988830650740445.stgit@djiang5-desk3.ch.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

d1dfe5b8 - dmaengine: idxd: add descriptor manipulation routines

Tue, 21 Jan 2020 23:44:17 +0000

dmaengine: idxd: add descriptor manipulation routinesThis commit adds helper functions for DSA descriptor allocation,submission, and free operations.Signed-off-by: Dave Jiang Link: https://lore.kernel.org/r/157965025757.73301.12692876585357550065.stgit@djiang5-desk3.ch.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

c52ca478 - dmaengine: idxd: add configuration component of driver

Tue, 21 Jan 2020 23:44:05 +0000

dmaengine: idxd: add configuration component of driverThe device is left unconfigured when the driver is loaded. Variouscomponents are configured via the driver sysfs attributes. Onceconfiguration is done, the device can be enabled by writing the device nameto the bind attribute of the device driver sysfs. Disabling can be donesimilarly. Also the individual work queues can also be enabled and disabledthrough the bind/unbind attributes. A constructed hierarchy is createdthrough the struct device framework in order to provide appropriateconfiguration points and device state and status. This hierarchy ispresented off the virtual DSA bus.i.e. /sys/bus/dsa/...Signed-off-by: Dave Jiang Link: https://lore.kernel.org/r/157965024585.73301.6431413676230150589.stgit@djiang5-desk3.ch.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile

bfe1d560 - dmaengine: idxd: Init and probe for Intel data accelerators

Tue, 21 Jan 2020 23:43:59 +0000

dmaengine: idxd: Init and probe for Intel data acceleratorsThe idxd driver introduces the Intel Data Stream Accelerator [1] that willbe available on future Intel Xeon CPUs. One of the kernel accesspoint for the driver is through the dmaengine subsystem. It will initiallyprovide the DMA copy service to the kernel.Some of the main functionality introduced with this acceleratorare: shared virtual memory (SVM) support, and descriptor submission usingIntel CPU instructions movdir64b and enqcmds. There will be additionalaccelerator devices that share the same driver with variations tocapabilities.This commit introduces the probe and initialization component of thedriver.[1]: https://software.intel.com/en-us/download/intel-data-streaming-accelerator-preliminary-architecture-specificationSigned-off-by: Dave Jiang Link: https://lore.kernel.org/r/157965023991.73301.6186843973135311580.stgit@djiang5-desk3.ch.intel.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/dma/idxd/Makefile