[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <144086DDB7BB6D429C79280EB1C804D40AB765C4@SHSMSX103.ccr.corp.intel.com>
Date: Tue, 26 Apr 2016 01:04:13 +0000
From: "Zhang, Yanmin" <yanmin.zhang@...el.com>
To: Afzal Mohammed <afzal.mohd.ma@...il.com>,
"Zhang, LongX" <longx.zhang@...el.com>
CC: "mingo@...hat.com" <mingo@...hat.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] sched: don't output cpu sched info by default
Thanks for the pointer. We didn't notice that. That patch also
fixes the issue indeed.
Yanmin
-----Original Message-----
From: Afzal Mohammed [mailto:afzal.mohd.ma@...il.com]
Sent: Monday, April 25, 2016 6:50 PM
To: Zhang, LongX
Cc: mingo@...hat.com; peterz@...radead.org; linux-kernel@...r.kernel.org; Zhang, Yanmin
Subject: Re: [PATCH] sched: don't output cpu sched info by default
Hi,
On Mon, Apr 25, 2016 at 01:04:41PM +0800, Zhang Long wrote:
> Android userspace debug prcoess might dump system info by sysrq.
> One info is of cpu sched. Usually, one thread has one line dump.
> Such log is huge sometimes and such dumping spends lots of time and
> make the system worse. Sometimes, watchdog resets the system in the
> end.
>
> The patch fixes it by dumping cpu sched info only when
> sched_debug_enabled is true.
Doesn't "sched: don't dump sched debug info in SysRq-W" currently in tip/sched/core help ?,
http://lkml.kernel.org/r/1459777322-30902-1-git-send-email-rabin.vincent@axis.com
Regards
afzal
Powered by blists - more mailing lists