Changes in Kconfig

26b3a37b - NTB: Introduce MSI library

Thu, 23 May 2019 22:30:56 +0000

NTB: Introduce MSI libraryThe NTB MSI library allows passing MSI interrupts across a memorywindow. This offers similar functionality to doorbells or messagesexcept will often have much better latency and the client canpotentially use significantly more remote interrupts than typical hardwareprovides for doorbells. (Which can be important in high-multiportsetups.)The library utilizes one memory window per peer and uses the highestindex memory windows. Before any ntb_msi function may be used, the usermust call ntb_msi_init(). It may then setup and tear down the memorywindows when the link state changes using ntb_msi_setup_mws() andntb_msi_clear_mws().The peer which receives the interrupt must call ntb_msim_request_irq()to assign the interrupt handler (this function is functionallysimilar to devm_request_irq()) and the returned descriptor must betransferred to the peer which can use it to trigger the interrupt.The triggering peer, once having received the descriptor, cantrigger the interrupt by calling ntb_msi_peer_trigger().Signed-off-by: Logan Gunthorpe Cc: Dave Jiang Cc: Allen Hubbe Signed-off-by: Jon Mason List of files: /linux-6.15/drivers/ntb/Kconfig

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/ntb/Kconfig

963de473 - NTB: Add ping pong test client

Wed, 15 Apr 2015 15:12:41 +0000

NTB: Add ping pong test clientThis is a simple ping pong driver that exercises the scratch pads anddoorbells of the ntb hardware. This driver may be used to test thatyour ntb hardware and drivers are functioning at a basic level.Signed-off-by: Allen Hubbe Signed-off-by: Jon Mason List of files: /linux-6.15/drivers/ntb/Kconfig

e26a5843 - NTB: Split ntb_hw_intel and ntb_transport drivers

Thu, 09 Apr 2015 14:33:20 +0000

NTB: Split ntb_hw_intel and ntb_transport driversChange ntb_hw_intel to use the new NTB hardware abstraction layer.Split ntb_transport into its own driver. Change it to use the new NTBhardware abstraction layer.Signed-off-by: Allen Hubbe Signed-off-by: Jon Mason List of files: /linux-6.15/drivers/ntb/Kconfig

ac477afb - NTB: Enable 32bit Support

Mon, 21 Jan 2013 23:40:39 +0000

NTB: Enable 32bit SupportCorrect the issues on NTB that prevented it from working on x86_32 andmodify the Kconfig to allow it to be permitted to be used in thatenvironment as well.Signed-off-by: Jon Mason List of files: /linux-6.15/drivers/ntb/Kconfig

719234f9 - NTB: disable x86_32 support

Mon, 21 Jan 2013 22:28:51 +0000

NTB: disable x86_32 supportAtomic readq and writeq do not exist by default on some 32bitarchitectures, thus causing compile errors due to non-existent symbols.Since NTB has not been tested 32bit, disable x86_32 support until suchtime as this and any other issues can be properly discovered.Signed-off-by: Jon Mason Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/ntb/Kconfig

fce8a7bb - PCI-Express Non-Transparent Bridge Support

Sat, 17 Nov 2012 02:27:12 +0000

PCI-Express Non-Transparent Bridge SupportA PCI-Express non-transparent bridge (NTB) is a point-to-point PCIe busconnecting 2 systems, providing electrical isolation between the two subsystems.A non-transparent bridge is functionally similar to a transparent bridge exceptthat both sides of the bridge have their own independent address domains. Thehost on one side of the bridge will not have the visibility of the completememory or I/O space on the other side of the bridge. To communicate across thenon-transparent bridge, each NTB endpoint has one (or more) apertures exposed tothe local system. Writes to these apertures are mirrored to memory on theremote system. Communications can also occur through the use of doorbellregisters that initiate interrupts to the alternate domain, and scratch-padregisters accessible from both sides.The NTB device driver is needed to configure these memory windows, doorbell, andscratch-pad registers as well as use them in such a way as they can be turnedinto a viable communication channel to the remote system. ntb_hw.[ch]determines the usage model (NTB to NTB or NTB to Root Port) and abstracts awaythe underlying hardware to provide access and a common interface to the doorbellregisters, scratch pads, and memory windows. These hardware interfaces areexported so that other, non-mainlined kernel drivers can access these.ntb_transport.[ch] also uses the exported interfaces in ntb_hw.[ch] to setup acommunication channel(s) and provide a reliable way of transferring data fromone side to the other, which it then exports so that "client" drivers can accessthem. These client drivers are used to provide a standard kernel interface(i.e., Ethernet device) to NTB, such that Linux can transfer data from onesystem to the other in a standard way.Signed-off-by: Jon Mason Reviewed-by: Nicholas Bellinger Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/ntb/Kconfig