<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/ntb, branch v3.10.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/ntb?h=v3.10.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/ntb?h=v3.10.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2013-05-15T17:58:22Z</updated>
<entry>
<title>NTB: Multiple NTB client fix</title>
<updated>2013-05-15T17:58:22Z</updated>
<author>
<name>Jon Mason</name>
<email>jon.mason@intel.com</email>
</author>
<published>2013-04-26T21:51:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8b19d450ad188d402a183ff4a4d40f31c3916fbf'/>
<id>urn:sha1:8b19d450ad188d402a183ff4a4d40f31c3916fbf</id>
<content type='text'>
Fix issue with adding multiple ntb client devices to the ntb virtual
bus.  Previously, multiple devices would be added with the same name,
resulting in crashes.  To get around this issue, add a unique number to
the device when it is added.

Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>NTB: memcpy lockup workaround</title>
<updated>2013-05-15T17:58:06Z</updated>
<author>
<name>Jon Mason</name>
<email>jon.mason@intel.com</email>
</author>
<published>2013-01-17T22:28:45Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c336acd3331dcc191a97dbc66a557d47741657c7'/>
<id>urn:sha1:c336acd3331dcc191a97dbc66a557d47741657c7</id>
<content type='text'>
The system will appear to lockup for long periods of time due to the NTB
driver spending too much time in memcpy.  Avoid this by reducing the
number of packets that can be serviced on a given interrupt.

Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>NTB: Correctly handle receive buffers of the minimal size</title>
<updated>2013-05-15T17:57:59Z</updated>
<author>
<name>Jon Mason</name>
<email>jon.mason@intel.com</email>
</author>
<published>2013-02-01T22:45:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=c9d534c8cbaedbb522a1d2cb037c6c394f610317'/>
<id>urn:sha1:c9d534c8cbaedbb522a1d2cb037c6c394f610317</id>
<content type='text'>
The ring logic of the NTB receive buffer/transmit memory window requires
there to be at least 2 payload sized allotments.  For the minimal size
case, split the buffer into two and set the transport_mtu to the
appropriate size.

Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>NTB: reset tx_index on link toggle</title>
<updated>2013-05-15T17:57:51Z</updated>
<author>
<name>Jon Mason</name>
<email>jon.mason@intel.com</email>
</author>
<published>2013-02-01T22:34:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=90f9e934647e652a69396e18c779215a493271cf'/>
<id>urn:sha1:90f9e934647e652a69396e18c779215a493271cf</id>
<content type='text'>
If the NTB link toggles, the driver could stop receiving due to the
tx_index not being set to 0 on the transmitting size on a link-up event.
This is due to the driver expecting the incoming data to start at the
beginning of the receive buffer and not at a random place.

Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>NTB: Link toggle memory leak</title>
<updated>2013-05-15T17:57:45Z</updated>
<author>
<name>Jon Mason</name>
<email>jon.mason@intel.com</email>
</author>
<published>2013-02-01T22:25:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b77b2637b39ecc380bb08992380d7d48452b0872'/>
<id>urn:sha1:b77b2637b39ecc380bb08992380d7d48452b0872</id>
<content type='text'>
Each link-up will allocate a new NTB receive buffer when the NTB
properties are negotiated with the remote system.  These allocations did
not check for existing buffers and thus did not free them.  Now, the
driver will check for an existing buffer and free it if not of the
correct size, before trying to alloc a new one.

Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>NTB: Handle 64bit BAR sizes</title>
<updated>2013-05-15T17:57:40Z</updated>
<author>
<name>Jon Mason</name>
<email>jon.mason@intel.com</email>
</author>
<published>2013-01-30T18:40:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=113fc505b83b2d16e820ca74fa07f99a34877b1d'/>
<id>urn:sha1:113fc505b83b2d16e820ca74fa07f99a34877b1d</id>
<content type='text'>
64bit BAR sizes are permissible with an NTB device.  To support them
various modifications and clean-ups were required, most significantly
using 2 32bit scratch pad registers for each BAR.

Also, modify the driver to allow more than 2 Memory Windows.

Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>NTB: fix pointer math issues</title>
<updated>2013-05-15T17:57:29Z</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2013-01-23T19:26:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cc0f868d8adef7bdc12cda132654870086d766bc'/>
<id>urn:sha1:cc0f868d8adef7bdc12cda132654870086d766bc</id>
<content type='text'>
-&gt;remote_rx_info and -&gt;rx_info are struct ntb_rx_info pointers.  If we
add sizeof(struct ntb_rx_info) then it goes too far.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>ntb: off by one sanity checks</title>
<updated>2013-05-15T17:57:24Z</updated>
<author>
<name>Dan Carpenter</name>
<email>dan.carpenter@oracle.com</email>
</author>
<published>2013-01-22T07:19:14Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ad3e2751e7c546ae678be1f8d86e898506b42cef'/>
<id>urn:sha1:ad3e2751e7c546ae678be1f8d86e898506b42cef</id>
<content type='text'>
These tests are off by one.  If "mw" is equal to NTB_NUM_MW then we
would go beyond the end of the ndev-&gt;mw[] array.

Signed-off-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>NTB: variable dereferenced before check</title>
<updated>2013-05-15T17:57:17Z</updated>
<author>
<name>Jon Mason</name>
<email>jon.mason@intel.com</email>
</author>
<published>2013-01-22T18:35:40Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=186f27ff9f9ec5c110739ced88ce9f8fca053882'/>
<id>urn:sha1:186f27ff9f9ec5c110739ced88ce9f8fca053882</id>
<content type='text'>
Correct instances of variable dereferencing before checking its value on
the functions exported to the client drivers.  Also, add sanity checks
for all exported functions.

Reported-by: Dan Carpenter &lt;dan.carpenter@oracle.com&gt;
Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
</content>
</entry>
<entry>
<title>NTB: Fix Sparse Warnings</title>
<updated>2013-01-21T22:34:21Z</updated>
<author>
<name>Jon Mason</name>
<email>jon.mason@intel.com</email>
</author>
<published>2013-01-21T22:28:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=74465645cdb4391b9fc95d12fd750a88012ad479'/>
<id>urn:sha1:74465645cdb4391b9fc95d12fd750a88012ad479</id>
<content type='text'>
Address the sparse warnings and resulting fallout

Signed-off-by: Jon Mason &lt;jon.mason@intel.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
