On 02/14/2012 10:29 AM, Sujith wrote: > Ben Greear wrote: >> Actually, I think it might be useful to have a second level of debugging. >> I hope to soon have time& resources to add some logic to dump lots of >> register >> info and such in human-readable format, (like, when DMA times out). That is >> going to be a lot >> of strings added to the driver, so the compile size will definitely >> increase. If keeping the size small is important, then this sort of verbose >> thing >> could be hidden behind a second level of debugging... > > That could be implemented similar to what usbmon does. A debugfs file that > could > be read and redirected to a file. And there would be no overhead to the > driver, I think. We could call it the 'event log'. :)
I was thinking about adding a method that grabbed as many registers as I have info for and dumping them with printk when DMA errors hit. This would make kernel splats more useful. And also have a debugfs file called 'registers' or similar that one could cat out and get similar info. And this can let folks look at steady-state or whatever. But, the logic to turn the register bit values into strings would be in the driver (and thus add some code size bloat). My hope is that this would allow a better chance of understanding the stop-DMA errors that some people get reliably (but which I can never reliably reproduce). I'm not sure how that plays into your 'event log' idea, but maybe one will help the other. Thanks, Ben -- Ben Greear <gree...@candelatech.com> Candela Technologies Inc http://www.candelatech.com _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
