Re: [RFC -v3 2/2] watchdog: update watchdog_tresh properly

2013-07-23 Thread Michal Hocko
On Tue 23-07-13 10:44:08, Don Zickus wrote: > On Tue, Jul 23, 2013 at 04:07:29PM +0200, Michal Hocko wrote: > > On Tue 23-07-13 09:53:34, Don Zickus wrote: > > > On Mon, Jul 22, 2013 at 04:32:46PM +0200, Michal Hocko wrote: > > > > The nmi one is disabled and then reinitialized from scratch. This >

Re: [RFC -v3 2/2] watchdog: update watchdog_tresh properly

2013-07-23 Thread Don Zickus
On Tue, Jul 23, 2013 at 04:07:29PM +0200, Michal Hocko wrote: > On Tue 23-07-13 09:53:34, Don Zickus wrote: > > On Mon, Jul 22, 2013 at 04:32:46PM +0200, Michal Hocko wrote: > > > The nmi one is disabled and then reinitialized from scratch. This > > > has an unpleasant side effect that the allocati

Re: [RFC -v3 2/2] watchdog: update watchdog_tresh properly

2013-07-23 Thread Michal Hocko
On Tue 23-07-13 09:53:34, Don Zickus wrote: > On Mon, Jul 22, 2013 at 04:32:46PM +0200, Michal Hocko wrote: > > The nmi one is disabled and then reinitialized from scratch. This > > has an unpleasant side effect that the allocation of the new event might > > fail theoretically so the hard lockup de

Re: [RFC -v3 2/2] watchdog: update watchdog_tresh properly

2013-07-23 Thread Don Zickus
On Mon, Jul 22, 2013 at 04:32:46PM +0200, Michal Hocko wrote: > The nmi one is disabled and then reinitialized from scratch. This > has an unpleasant side effect that the allocation of the new event might > fail theoretically so the hard lockup detector would be disabled for > such cpus. On the oth