diff options
author | Jiang Liu <jiang.liu@linux.intel.com> | 2015-07-08 15:41:42 +0800 |
---|---|---|
committer | Vinod Koul <vinod.koul@intel.com> | 2015-07-16 18:28:28 +0530 |
commit | b6c52c634506d52b3a2dc18503980d717e478739 (patch) | |
tree | 751c0c1fd2b536507355bc4ed5f85c5e005e8e21 /drivers/dma/hsu | |
parent | 7618d0359c167d89d7e904a00487be4945c10a65 (diff) |
dmaengine: ioatdma: Ignore IOAT devices under hotplug-capable PCI host bridge
The dmaengine core assumes that async DMA devices will only be removed
when they not used anymore, or it assumes dma_async_device_unregister()
will only be called by dma driver exit routines. But this assumption is
not true for the IOAT driver, which calls dma_async_device_unregister()
from ioat_remove(). So current IOAT driver doesn't support device
hot-removal because it may cause system crash to hot-remove an inuse
IOAT device.
To support CPU socket hot-removal, all PCI devices, including IOAT
devices embedded in the socket, will be hot-removed. The idea solution
is to enhance the dmaengine core and IOAT driver to support hot-removal,
but that's too hard.
This patch implements a hack to disable IOAT devices under hotplug-capable
CPU socket so it won't break socket hot-removal.
Signed-off-by: Jiang Liu <jiang.liu@linux.intel.com>
Signed-off-by: Vinod Koul <vinod.koul@intel.com>
Diffstat (limited to 'drivers/dma/hsu')
0 files changed, 0 insertions, 0 deletions