From: Andrew Morton <akpm@linux-foundation.org>
To: Sameer Nanda <snanda@chromium.org>
Cc: mingo@redhat.com, peterz@infradead.org, len.brown@intel.com,
pavel@ucw.cz, rjw@sisk.pl, dzickus@redhat.com, msb@chromium.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
olofj@chromium.org
Subject: Re: [PATCH] watchdog: fix for lockup detector breakage on resume
Date: Fri, 27 Apr 2012 15:03:30 -0700 [thread overview]
Message-ID: <20120427150330.783a5b97.akpm@linux-foundation.org> (raw)
In-Reply-To: <CANMivWaAN9D=-BjSP=frHijWK+K3abAo9nCuW8o+rPSDdHgm7g@mail.gmail.com>
On Fri, 27 Apr 2012 14:40:01 -0700
Sameer Nanda <snanda@chromium.org> wrote:
> On Fri, Apr 27, 2012 at 2:12 PM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
>
> This call actually happens on "exit from suspend" or "entry into
> resume" processing so
> how about something like:
>
> On exit from suspend we force an offline->online transition on the boot CPU so
> that the PMU state that was lost while in suspended state gets set up properly
> for the boot CPU. This information is required for restarting the NMI watchdog.
OK, let's use that.
> > Also, this is all dead code if CONFIG_SUSPEND=n, so how about
> >
You had no comments about this?
next prev parent reply other threads:[~2012-04-27 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 18:10 [PATCH] watchdog: fix for lockup detector breakage on resume Sameer Nanda
2012-04-27 21:12 ` Andrew Morton
2012-04-27 21:33 ` Rafael J. Wysocki
2012-04-27 21:40 ` Sameer Nanda
2012-04-27 22:03 ` Andrew Morton [this message]
2012-04-27 22:20 ` Sameer Nanda
2012-04-30 6:12 ` Srivatsa S. Bhat
2012-04-30 13:05 ` Don Zickus
2012-04-30 21:10 ` Sameer Nanda
2012-05-01 17:25 ` Sameer Nanda
2012-05-02 13:14 ` Srivatsa S. Bhat
2012-05-01 17:22 ` [PATCH v2] " Sameer Nanda
2012-05-07 3:24 ` Anshuman Khandual
2012-06-08 21:44 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120427150330.783a5b97.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dzickus@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=msb@chromium.org \
--cc=olofj@chromium.org \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rjw@sisk.pl \
--cc=snanda@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox