[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160323075359.GH6356@twins.programming.kicks-ass.net>
Date: Wed, 23 Mar 2016 08:53:59 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc: Chris Metcalf <cmetcalf@...lanox.com>,
Russell King <linux@....linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
Aaron Tomlin <atomlin@...hat.com>,
Ingo Molnar <mingo@...hat.com>, Andrew Morton <akpm@...l.org>,
Daniel Thompson <daniel.thompson@...aro.org>, x86@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-arch@...r.kernel.org
Subject: Re: [PATCH v3 4/4] nmi_backtrace: generate one-line reports for idle
cpus
On Wed, Mar 23, 2016 at 01:50:00AM +0100, Rafael J. Wysocki wrote:
> > > Well, what about intel_idle_freeze()? Or do we not care?
> >
> > I argued against it; when you're suspended the NMI watchdog is stopped
> > too.
>
> Is it also stopped for suspend-to-idle? I'm not sure about that.
>
> Where do I need to look to find out?
Hmm I have memories of writing a patch to that effect when we were
starting with that suspend-to-idle stuff, because people didn't like
being woken up all the time.
But now that I look I cannot find it either..
Powered by blists - more mailing lists