[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4FA74089.4080204@linux.vnet.ibm.com>
Date: Mon, 07 May 2012 08:54:57 +0530
From: Anshuman Khandual <khandual@...ux.vnet.ibm.com>
To: Sameer Nanda <snanda@...omium.org>
CC: mingo@...hat.com, peterz@...radead.org, len.brown@...el.com,
pavel@....cz, rjw@...k.pl, akpm@...ux-foundation.org,
dzickus@...hat.com, msb@...omium.org, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, olofj@...omium.org,
"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>
Subject: Re: [PATCH v2] watchdog: fix for lockup detector breakage on resume
On Tuesday 01 May 2012 10:52 PM, Sameer Nanda wrote:
> On the suspend/resume path the boot CPU does not go though an
> offline->online transition. This breaks the NMI detector
> post-resume since it depends on PMU state that is lost when
> the system gets suspended.
We should not have allowed the PMU to go with events counting on it across the suspend/resume transition
and find out that the state has been lost. This patch solves the problem of the NMI detector as we restart the
counter again when the boot cpu comes back online during resume. But the original cause (PMU going with
counters into the suspend state) which triggered this problem is still there. May be we should have called
perf_event_exit() on the boot cpu before going into the suspend state.
Regards
Anshuman
--
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