linux/drivers/ntb/test, branch v4.7

NTB: Fix incorrect clean up routine in ntb_perf

2016-03-21T23:28:30Z

The clean up routine when we failed to allocate kthread is not cleaning up all the threads, only the same one over and over again. Reported-by: Dan Carpenter Signed-off-by: Dave Jiang Acked-by: Allen Hubbe Signed-off-by: Jon Mason

NTB: Fix incorrect return check in ntb_perf

2016-03-21T23:28:25Z

kthread_create_no_node() returns error pointers, never NULL. Fix check so it handles error correctly. Reported-by: Dan Carpenter Signed-off-by: Dave Jiang Signed-off-by: Jon Mason

ntb: fix possible NULL dereference

2016-03-18T00:52:15Z

kmalloc can fail and we should check for NULL before using the pointer returned by kmalloc. Signed-off-by: Sudip Mukherjee Acked-by: Dave Jiang Signed-off-by: Jon Mason

ntb: add missing setup of translation window

2016-03-18T00:50:15Z

The perf tool is missing the setup of translation window. Adding call to setup the translation window for backed memory. Signed-off-by: John Kading Signed-off-by: Dave Jiang Signed-off-by: Jon Mason

ntb: perf test: fix address space confusion

2016-03-18T00:38:40Z

The ntb driver assigns between pointers an __iomem tokens, and also casts them to 64-bit integers, which results in compiler warnings on 32-bit systems: drivers/ntb/test/ntb_perf.c: In function 'perf_copy': drivers/ntb/test/ntb_perf.c:213:10: error: cast from pointer to integer of different size [-Werror=pointer-to-int-cast] vbase = (u64)(u64 *)mw->vbase; ^ drivers/ntb/test/ntb_perf.c:214:14: error: cast from pointer to integer of different size [-Werror=pointer-to-int-cast] dst_vaddr = (u64)(u64 *)dst; ^ This adds __iomem annotations where needed and changes the temporary variables to iomem pointers to avoid casting them to u64. I did not see the problem in linux-next earlier, but it show showed up in 4.5-rc1. Signed-off-by: Arnd Bergmann Acked-by: Dave Jiang Fixes: 8a7b6a778a85 ("ntb: ntb perf tool") Signed-off-by: Jon Mason

ntb: ntb perf tool

2016-01-18T03:08:05Z

Providing raw performance data via a tool that directly access data from NTB w/o any software overhead. This allows measurement of the hardware performance limit. In revision one we are only doing single direction CPU and DMA writes. Eventually we will provide bi-directional writes. The measurement using DMA engine for NTB performance measure does not measure the raw performance of DMA engine over NTB due to software overhead. But it should provide the peak performance through the Linux DMA driver. Signed-off-by: Dave Jiang Tested-by: Allen Hubbe Signed-off-by: Jon Mason

NTB: Add tool test client

2015-07-04T18:08:17Z

This is a simple debugging driver that enables the doorbell and scratch pad registers to be read and written from the debugfs. This tool enables more complicated debugging to be scripted from user space. This driver may be used to test that your ntb hardware and drivers are functioning at a basic level. Signed-off-by: Allen Hubbe Signed-off-by: Jon Mason

NTB: Add ping pong test client

2015-07-04T18:07:42Z

This is a simple ping pong driver that exercises the scratch pads and doorbells of the ntb hardware. This driver may be used to test that your ntb hardware and drivers are functioning at a basic level. Signed-off-by: Allen Hubbe Signed-off-by: Jon Mason