Hi! > spin_dump() and trigger_all_cpu_backtrace() result in a bunch of > additional printk()-s so CPU0 has even more job to do in console_unlock(), > while it still holds the contended spin_lock. and so on; there are > many other examples. > > so should we declare a "we can spend only 2 seconds in direct printk() > and then must offload printing" rule? I don't think it's much better > than a simpler "we always offload, as long as we think it's safe".
I believe we should do the 2 seconds rule. It allows us to print "some messages delayed" message, so at least whoever is trying to debug the crash will have the hints that he needs to look at the printk system. "we always offload, as long as we think it's safe" rule does not really work, as printk() can not detect if it is safe or not. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
signature.asc
Description: Digital signature