Messages in this thread | | | Date | Sun, 25 Apr 2010 23:24:46 -0700 | Subject | Re: [PATCH 5/9] PM: suspend_block: Add debugfs file | From | Brian Swetland <> |
| |
On Sun, Apr 25, 2010 at 12:53 PM, Randy Dunlap <randy.dunlap@oracle.com> wrote: > On 04/25/10 11:15, Greg KH wrote: >> On Fri, Apr 23, 2010 at 01:58:53PM -0700, Randy Dunlap wrote: >>> On Thu, 22 Apr 2010 18:08:54 -0700 Arve Hj?nnev?g wrote: >>> >>>> Report active and inactive suspend blockers in >>>> /sys/kernel/debug/suspend_blockers. >>> >>> >>> This looks more like user interface information than it does debug information. >>> If that's correct, it shouldn't be in debugfs. >> >> It's debug-like information, and has more than one value per file, so >> debugfs seems like the proper place for it. I have no objection to it >> going there. > > I have no objection if it really is debug info, but I'm not convinced > of that yet.
Our most common use of this information is to capture it in bugreports (along with process lists, system/radio logs, memory stats, etc) as one additional piece of data used to diagnose a misbehaving device (most commonly to answer the "why does the battery seem to be draining too quickly?" question).
Brian -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |