06 Feb, 2010
1 commit
-
Use DECLARE_WAIT_QUEUE_HEAD_ONSTACK to make lockdep happy
Signed-off-by: Yong Zhang
Cc: Maciej Sosnowski
Cc: Andrew Morton
Cc: Nicolas Ferre
Signed-off-by: Dan Williams
11 Dec, 2009
1 commit
-
Transfers and the test buffer have to be at least align bytes long.
Signed-off-by: Guennadi Liakhovetski
Signed-off-by: Dan Williams
09 Sep, 2009
3 commits
-
Conflicts:
crypto/async_tx/async_xor.c
drivers/dma/ioat/dma_v2.h
drivers/dma/ioat/pci.c
drivers/md/raid5.c -
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
-
Conflicts:
include/linux/dmaengine.h
30 Aug, 2009
1 commit
-
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
Acked-by: Maciej Sosnowski
Signed-off-by: Dan Williams
23 Jul, 2009
3 commits
-
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
Acked-by: Haavard Skinnemoen
Acked-by: Maciej Sosnowski
Signed-off-by: Andrew Morton
Signed-off-by: Dan Williams -
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
Cc: Haavard Skinnemoen
Acked-by: Maciej Sosnowski
Signed-off-by: Andrew Morton
Signed-off-by: Dan Williams -
Signed-off-by: Joe Perches
Signed-off-by: Dan Williams
09 Apr, 2009
1 commit
-
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:
Reported-by: Dan Carpenter
Signed-off-by: Dan Williams
26 Mar, 2009
2 commits
-
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
-
Extend dmatest to launch a thread per supported operation type and add
an xor test.Signed-off-by: Dan Williams
05 Mar, 2009
1 commit
-
dmatest_cleanup_chanel will free dtc, so grab ->chan before it goes away
and use it to do the release.Reported-by: Thierry Reding
Signed-off-by: Dan Williams
14 Jan, 2009
1 commit
-
The dmatest driver should use DMA_BIDIRECTIONAL on the destination buffer
to ensure that the poison values are written to RAM and not just written
to cache and discarded.Acked-by: Haavard Skinnemoen
Acked-by: Maciej Sosnowski
Signed-off-by: Atsushi Nemoto
Signed-off-by: Dan Williams
07 Jan, 2009
4 commits
-
Resolves:
WARNING: at drivers/base/core.c:122 device_release+0x4d/0x52()
Device 'dma0chan0' does not have a release() function, it is broken and must be fixed.The dma_chan_dev object is introduced to gear-match sysfs kobject and
dmaengine channel lifetimes. When a channel is removed access to the
sysfs entries return -ENODEV until the kobject can be released.The bulk of the change is updates to existing code to handle the extra
layer of indirection between a dma_chan and its struct device.Reported-by: Alexander Beregalov
Acked-by: Stephen Hemminger
Cc: Haavard Skinnemoen
Signed-off-by: Dan Williams -
DMA_NAK is now useless. We can just use a bool instead.
Reviewed-by: Andrew Morton
Signed-off-by: Dan Williams -
Replace the client registration infrastructure with a custom loop to
poll for channels. Once dma_request_channel returns NULL stop asking
for channels. A userspace side effect of this change if that loading
the dmatest module before loading a dma driver will result in no
channels being found, previously dmatest would get a callback. To
facilitate testing in the built-in case dmatest_init is marked as a
late_initcall. Another side effect is that channels under test can not
be used for any other purpose.Cc: Haavard Skinnemoen
Reviewed-by: Andrew Morton
Signed-off-by: Dan Williams -
Simply, if a client wants any dmaengine channel then prevent all dmaengine
modules from being removed. Once the clients are done re-enable module
removal.Why?, beyond reducing complication:
1/ Tracking reference counts per-transaction in an efficient manner, as
is currently done, requires a complicated scheme to avoid cache-line
bouncing effects.
2/ Per-transaction ref-counting gives the false impression that a
dma-driver can be gracefully removed ahead of its user (net, md, or
dma-slave)
3/ None of the in-tree dma-drivers talk to hot pluggable hardware, but
if such an engine were built one day we still would not need to notify
clients of remove events. The driver can simply return NULL to a
->prep() request, something that is much easier for a client to handle.Reviewed-by: Andrew Morton
Acked-by: Maciej Sosnowski
Signed-off-by: Dan Williams
12 Nov, 2008
1 commit
-
Acked-by: Greg Kroah-Hartman
Acked-by: Maciej Sosnowski
Signed-off-by: Kay Sievers
Signed-off-by: Dan Williams
19 Sep, 2008
2 commits
-
It was needlessly using the unreliable GFP_ATOMIC.
Cc: Timur Tabi
Acked-by: Haavard Skinnemoen
Signed-off-by: Andrew Morton
Signed-off-by: Dan Williams -
Update the the dmatest driver so that it handles duplicate DMA channels
properly.When a DMA client is notified of an available DMA channel, it must check if it
has already allocated resources for that channel. If so, it should return
DMA_DUP. This can happen, for example, if a DMA driver calls
dma_async_device_register() more than once.Acked-by: Haavard Skinnemoen
Signed-off-by: Timur Tabi
Signed-off-by: Dan Williams
09 Jul, 2008
1 commit
-
This client tests DMA memcpy using various lengths and various offsets
into the source and destination buffers. It will initialize both
buffers with a repeatable pattern and verify that the DMA engine copies
the requested region and nothing more. It will also verify that the
bytes aren't swapped around, and that the source buffer isn't modified.The dmatest module can be configured to test a specific device, a
specific channel. It can also test multiple channels at the same time,
and it can start multiple threads competing for the same channel.Changes since v2:
* Support testing multiple channels at the same time
* Support testing with multiple threads competing for the same channel
* Use counting test patterns in order to catch byte ordering issuesChanges since v1:
* Remove extra dashes around "help"
* Remove "default n" from Kconfig
* Turn TEST_BUF_SIZE into a module parameter
* Return DMA_NAK instead of DMA_DUP
* Print unhandled events
* Support testing specific channels and devices
* Move to the end of the MakefileAcked-by: Maciej Sosnowski
Signed-off-by: Haavard Skinnemoen
Signed-off-by: Dan Williams
