Tejun Heo wrote:
Alan Cox wrote:
This is useful when debugging, handling problem systems, or for
distributions just to get the system installed so it can be sorted
out later.
This is a bit smarter than the old IDE one and lets you do
libata.pata_dma=0 Disable all PATA DMA like old IDE
libata.pata_dma=1 Disk DMA only
libata.pata_dma=2 ATAPI DMA only
libata.pata_dma=4 CF DMA only
(or combinations thereof - 0,1,3 being the useful ones I suspect)
(I've split CF as it seems to be a seperate case of pain and suffering
different to the others and caused by assorted PIO wired adapters etc)
SATA is not affected - for one its not clear it makes sense to disable
DMA for SATA if even always possible, for two we've seen no failure
evidence to justify needing to support this kind of hammer on SATA.
Signed-off-by: Alan Cox <alan@xxxxxxxxxx>
Acked-by: Tejun Heo <htejun@xxxxxxxxx>
FWIW -- as I noted to Alan personally at KS, I would rather drop the
"pata_" and have it apply to all, PATA or SATA.
It is far less useful on SATA, but I can still see a possibility that
somebody might want to avoid DMA for whatever reason, chiefly, possibly
keeping failing hardware alive by slowing things down via PIO. And
being able to avoid the DMA protocols can be useful for debugging or
other things.
As an aside, it would be nice to get the EH in shape where it can pause
all ports, so we can finally allow userspace to submit SET FEATURES -
XFER MODE and have it handled cleanly and properly.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
