[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <33AB447FBD802F4E932063B962385B3512D9615B4D@shsmsx501.ccr.corp.intel.com>
Date: Fri, 5 Aug 2011 09:59:39 +0800
From: "Zhang, Yanmin" <yanmin.zhang@...el.com>
To: Dave Jones <davej@...hat.com>
CC: Linux Kernel <linux-kernel@...r.kernel.org>,
"Nguyen, Tom L" <tom.l.nguyen@...el.com>,
"Huang, Ying" <ying.huang@...el.com>
Subject: RE: [rfc] suppress excessive AER output
Dave,
My idea is application has opportunity to reset it. Consider the critical mission environment, admin could hot-unplug any failed devices without rebooting system. Then, admin doesn't want to lose AER monitoring.
With the module parameter, admin could change it under /sys/module/aer_drv/parameters.
Yanmin
-----Original Message-----
From: Dave Jones [mailto:davej@...hat.com]
Sent: Friday, August 05, 2011 9:50 AM
To: Zhang, Yanmin
Cc: Linux Kernel; Nguyen, Tom L; Huang, Ying
Subject: Re: [rfc] suppress excessive AER output
On Thu, Aug 04, 2011 at 01:54:19PM +0800, Zhang, Yanmin wrote:
> Dave,
>
> How about adding a new module parameter aer_printk_limit, so user space could reset it any time?
Sure. Though for the built-in case, how would that work ?
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists