<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>26b3a37b - NTB: Introduce MSI library</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/ntb/Makefile#26b3a37b</link>
        <description>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 &lt;logang@deltatee.com&gt;Cc: Dave Jiang &lt;dave.jiang@intel.com&gt;Cc: Allen Hubbe &lt;allenbh@gmail.com&gt;Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt;

            List of files:
            /linux-6.15/drivers/ntb/Makefile</description>
        <pubDate>Thu, 23 May 2019 22:30:56 +0000</pubDate>
        <dc:creator>Logan Gunthorpe &lt;logang@deltatee.com&gt;</dc:creator>
    </item>
<item>
        <title>d217e07b - NTB: Rename ntb.c to support multiple source files in the module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/ntb/Makefile#d217e07b</link>
        <description>NTB: Rename ntb.c to support multiple source files in the moduleThe kbuild system does not support having multiple source files ina module if one of those source files has the same name as the module.Therefore, we must rename ntb.c to core.c, while the module remainsntb.ko.This is similar to the way the nvme modules are structured.Signed-off-by: Logan Gunthorpe &lt;logang@deltatee.com&gt;Cc: Dave Jiang &lt;dave.jiang@intel.com&gt;Cc: Allen Hubbe &lt;allenbh@gmail.com&gt;Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt;

            List of files:
            /linux-6.15/drivers/ntb/Makefile</description>
        <pubDate>Thu, 23 May 2019 22:30:55 +0000</pubDate>
        <dc:creator>Logan Gunthorpe &lt;logang@deltatee.com&gt;</dc:creator>
    </item>
<item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/ntb/Makefile#ec8f24b7</link>
        <description>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 &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/ntb/Makefile</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>963de473 - NTB: Add ping pong test client</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/ntb/Makefile#963de473</link>
        <description>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 &lt;Allen.Hubbe@emc.com&gt;Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt;

            List of files:
            /linux-6.15/drivers/ntb/Makefile</description>
        <pubDate>Wed, 15 Apr 2015 15:12:41 +0000</pubDate>
        <dc:creator>Allen Hubbe &lt;Allen.Hubbe@emc.com&gt;</dc:creator>
    </item>
<item>
        <title>e26a5843 - NTB: Split ntb_hw_intel and ntb_transport drivers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/ntb/Makefile#e26a5843</link>
        <description>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 &lt;Allen.Hubbe@emc.com&gt;Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt;

            List of files:
            /linux-6.15/drivers/ntb/Makefile</description>
        <pubDate>Thu, 09 Apr 2015 14:33:20 +0000</pubDate>
        <dc:creator>Allen Hubbe &lt;Allen.Hubbe@emc.com&gt;</dc:creator>
    </item>
<item>
        <title>a1bd3bae - NTB: Add NTB hardware abstraction layer</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/ntb/Makefile#a1bd3bae</link>
        <description>NTB: Add NTB hardware abstraction layerAbstract the NTB device behind a programming interface, so that it cansupport different hardware and client drivers.Signed-off-by: Allen Hubbe &lt;Allen.Hubbe@emc.com&gt;Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt;

            List of files:
            /linux-6.15/drivers/ntb/Makefile</description>
        <pubDate>Thu, 09 Apr 2015 14:33:20 +0000</pubDate>
        <dc:creator>Allen Hubbe &lt;Allen.Hubbe@emc.com&gt;</dc:creator>
    </item>
<item>
        <title>ec110bc7 - NTB: Move files in preparation for NTB abstraction</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/ntb/Makefile#ec110bc7</link>
        <description>NTB: Move files in preparation for NTB abstractionThis patch only moves files to their new locations, before applying thenext two patches adding the NTB Abstraction layer.  Splitting this patchfrom the next is intended make distinct which code is changed only dueto moving the files, versus which are substantial code changes in addingthe NTB Abstraction layer.Signed-off-by: Allen Hubbe &lt;Allen.Hubbe@emc.com&gt;Signed-off-by: Jon Mason &lt;jdmason@kudzu.us&gt;

            List of files:
            /linux-6.15/drivers/ntb/Makefile</description>
        <pubDate>Thu, 07 May 2015 10:45:21 +0000</pubDate>
        <dc:creator>Allen Hubbe &lt;Allen.Hubbe@emc.com&gt;</dc:creator>
    </item>
<item>
        <title>fce8a7bb - PCI-Express Non-Transparent Bridge Support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/ntb/Makefile#fce8a7bb</link>
        <description>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 &quot;client&quot; 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 &lt;jon.mason@intel.com&gt;Reviewed-by: Nicholas Bellinger &lt;nab@linux-iscsi.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/ntb/Makefile</description>
        <pubDate>Sat, 17 Nov 2012 02:27:12 +0000</pubDate>
        <dc:creator>Jon Mason &lt;jon.mason@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
