linux.git/drivers/dma/dmatest.c, branch v2.6.32 Linux kernel source tree Merge branch 'dmaengine' into async-tx-next 2009-09-09T00:55:21+00:00 Dan Williams dan.j.williams@intel.com 2009-09-09T00:55:21+00:00 bbb20089a3275a19e475dbc21320c3742e3ca423 Conflicts: crypto/async_tx/async_xor.c drivers/dma/ioat/dma_v2.h drivers/dma/ioat/pci.c drivers/md/raid5.c 
Conflicts:
	crypto/async_tx/async_xor.c
	drivers/dma/ioat/dma_v2.h
	drivers/dma/ioat/pci.c
	drivers/md/raid5.c
dmaengine, async_tx: support alignment checks 2009-09-09T00:42:53+00:00 Dan Williams dan.j.williams@intel.com 2009-09-09T00:42:53+00:00 83544ae9f3991bfc7d5e0fe9a3008cd05a8d57b7 Some engines have transfer size and address alignment restrictions. Add a per-operation alignment property to struct dma_device that the async routines and dmatest can use to check alignment capabilities. Signed-off-by: Dan Williams <dan.j.williams@intel.com> 
Some engines have transfer size and address alignment restrictions.  Add
a per-operation alignment property to struct dma_device that the async
routines and dmatest can use to check alignment capabilities.

Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Merge branch 'md-raid6-accel' into ioat3.2 2009-09-09T00:42:29+00:00 Dan Williams dan.j.williams@intel.com 2009-09-09T00:42:29+00:00 f9dd2134374c8de6b911e2b8652c6c9622eaa658 Conflicts: include/linux/dmaengine.h 
Conflicts:
	include/linux/dmaengine.h
dmatest: add pq support 2009-08-30T02:09:27+00:00 Dan Williams dan.j.williams@intel.com 2009-08-30T02:09:27+00:00 58691d64c44ae41ddf098ecb31e9a994026e3cff Test raid6 p+q operations with a simple "always multiply by 1" q calculation to fit into dmatest's current destination verification scheme. Reviewed-by: Andre Noll <maan@systemlinux.org> Acked-by: Maciej Sosnowski <maciej.sosnowski@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> 
Test raid6 p+q operations with a simple "always multiply by 1" q
calculation to fit into dmatest's current destination verification
scheme.

Reviewed-by: Andre Noll <maan@systemlinux.org>
Acked-by: Maciej Sosnowski <maciej.sosnowski@intel.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
dmaengine: dmatest: correct thread_count while using multiple thread per channel 2009-07-23T05:11:28+00:00 Nicolas Ferre nicolas.ferre@atmel.com 2009-07-06T16:19:44+00:00 f1aef8b6e6abf32a3a269542f95a19e2cb319f6c It seems that thread_count is not properly calculated in dmatest. In fact the thread count number that is returned from dmatest_add_threads() is not correctly added to the thread_count and thus not properly printed. Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com> Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> Acked-by: Maciej Sosnowski <maciej.sosnowski@intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Dan Williams <dan.j.williams@intel.com> 
It seems that thread_count is not properly calculated in dmatest.
In fact the thread count number that is returned from dmatest_add_threads() is
not correctly added to the thread_count and thus not properly printed.

Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Acked-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Acked-by: Maciej Sosnowski <maciej.sosnowski@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
dmaengine: dmatest: add a maximum number of test iterations 2009-07-23T05:05:26+00:00 Nicolas Ferre nicolas.ferre@atmel.com 2009-07-03T17:26:51+00:00 0a2ff57d6fba92842272889b4bca447344cd9d36 The dmatest usually waits for the killing of its kthreads to stop running tests. This patch adds a parameter that sets a maximum number of test iterations. This feature is quite interesting for debugging when you set a lot of traces in your dmaengine controller driver. Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com> Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> Acked-by: Maciej Sosnowski <maciej.sosnowski@intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Dan Williams <dan.j.williams@intel.com> 
The dmatest usually waits for the killing of its kthreads to stop
running tests.  This patch adds a parameter that sets a maximum
number of test iterations.

This feature is quite interesting for debugging when you set a lot of
traces in your dmaengine controller driver.

Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Acked-by: Maciej Sosnowski <maciej.sosnowski@intel.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
drivers/dma: Remove unnecessary semicolons 2009-07-23T04:29:16+00:00 Joe Perches joe@perches.com 2009-06-28T16:26:21+00:00 c019894efc9c9ba5939948caa78c133b1ec8ae63 Signed-off-by: Joe Perches <joe@perches.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> 
Signed-off-by: Joe Perches <joe@perches.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
dmatest: fix max channels handling 2009-04-08T22:08:23+00:00 Dan Williams dan.j.williams@intel.com 2009-04-08T22:08:23+00:00 c56c81abe7e684bc6203632d807303eb765690dc The check for reaching max_channels is short circuited by 'continuing' after successfully adding a channel. [ Impact: make the 'max_channels' module parameter actually have an effect ] Cc: <stable@kernel.org> Reported-by: Dan Carpenter <error27@gmail.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com> 
The check for reaching max_channels is short circuited by 'continuing'
after successfully adding a channel.

[ Impact: make the 'max_channels' module parameter actually have an effect ]

Cc: <stable@kernel.org>
Reported-by: Dan Carpenter <error27@gmail.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
dmatest: add dma interrupts and callbacks 2009-03-25T16:13:25+00:00 Dan Williams dan.j.williams@intel.com 2009-03-25T16:13:25+00:00 e44e0aa3cfa97cddff01704751a4b25151830c72 Use the callback infrastructure to report driver/hardware hangs or missed interrupts. Since this makes the test threads much more aggressive (from: explicit 1ms sleep to: wait_for_completion) we set the nice value to 10 so as to not swamp legitimate tasks. Signed-off-by: Dan Williams <dan.j.williams@intel.com> 
Use the callback infrastructure to report driver/hardware hangs or
missed interrupts.  Since this makes the test threads much more
aggressive (from: explicit 1ms sleep to: wait_for_completion) we set the
nice value to 10 so as to not swamp legitimate tasks.

Signed-off-by: Dan Williams <dan.j.williams@intel.com>
dmatest: add xor test 2009-03-25T16:13:25+00:00 Dan Williams dan.j.williams@intel.com 2009-03-25T16:13:25+00:00 b54d5cb9156868fb4f27ccd46a3afb0bf3ef8e0c Extend dmatest to launch a thread per supported operation type and add an xor test. Signed-off-by: Dan Williams <dan.j.williams@intel.com> 
Extend dmatest to launch a thread per supported operation type and add
an xor test.

Signed-off-by: Dan Williams <dan.j.williams@intel.com>