Mon Sep 11 22:31:42 2017 UTC ()
doesn't seem the freeze/thaw in error recovery can cause the thread to panic,
all commands within are executed as polled and hence thread is not invoked


(jdolecek)
diff -r1.1.2.39 -r1.1.2.40 src/sys/dev/ata/TODO.ncq
cvs diff -r1.1.2.39 -r1.1.2.40 src/sys/dev/ata/Attic/TODO.ncq (expand / switch to unified diff)

--- src/sys/dev/ata/Attic/TODO.ncq 2017/09/11 22:30:05 1.1.2.39
+++ src/sys/dev/ata/Attic/TODO.ncq 2017/09/11 22:31:42 1.1.2.40
@@ -1,19 +1,17 @@ @@ -1,19 +1,17 @@
1Bugs 1Bugs
2---- 2----
3test wd* at umass?, confirm the ata_channel kludge works 3test wd* at umass?, confirm the ata_channel kludge works
4 4
5reconsider freeze/thaw in error recovery - can it screw up with thread? 
6 
7Other random notes (do outside the NCQ branch): 5Other random notes (do outside the NCQ branch):
8----------------------------------------------------- 6-----------------------------------------------------
9do biodone() in wddone() starting the dump to not leak bufs when dumping from 7do biodone() in wddone() starting the dump to not leak bufs when dumping from
10active system? make sure to not trigger atastart() 8active system? make sure to not trigger atastart()
11- call ata_kill_active() + ata_kill_pending() when dumping 9- call ata_kill_active() + ata_kill_pending() when dumping
12 10
13implement support for PM FIS-based switching, remove restriction in atastart() 11implement support for PM FIS-based switching, remove restriction in atastart()
14for hw which supports it, adjust error handling in controller drivers to handle 12for hw which supports it, adjust error handling in controller drivers to handle
15xfers for several different drives 13xfers for several different drives
16 14
17maybe do device error handling in not-interrupt-context (maybe this should be 15maybe do device error handling in not-interrupt-context (maybe this should be
18done on a mpata branch?) 16done on a mpata branch?)
19 17