linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lianwei Wang <lianwei.wang@gmail.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>, Oleg Nesterov <oleg@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [PATCH v1] PM / sleep: make pm notifier called symmetrically
Date: Mon, 6 Jun 2016 22:41:25 -0700	[thread overview]
Message-ID: <CAJFUiJhKJT5W_fq_hMGSG7rCUU4dx9o-H5SLiYWmktem2faj1w@mail.gmail.com> (raw)
In-Reply-To: <CAJFUiJiuzDL9Cu5rNBXbTo9CH2hS9VuNpuV3uqZC6rkqfQMzZg@mail.gmail.com>

On Wed, May 18, 2016 at 11:06 PM, Lianwei Wang <lianwei.wang@gmail.com> wrote:
> On Wed, May 18, 2016 at 1:34 PM, Rafael J. Wysocki <rafael@kernel.org> wrote:
>> On Wed, May 18, 2016 at 8:07 AM, Lianwei Wang <lianwei.wang@gmail.com> wrote:
>>> This makes pm notifier PREPARE/POST symmetrical: if PREPARE
>>> fails, we will only undo what ever happened on PREPARE.
>>>
>>> It fixes the unbalanced cpu hotplug enable in cpu pm notifier.
>>
>> Can you please describe the problem you're trying to address in a bit
>> more detail?
>
> It is described in another patch, and it is a common issue. I fixed
> the similar issue several times, all because that the CPU_POST_SUSPEND
> notifier callback is called without call CPU_SUSPEND_PREPARE notifier
> callback before. Something is DO in PM_XXX_PREPARE and UNDO in
> POST_XXX. If we don't DO it in XXX_PREPARE then we don't need to UNDO
> it in  PM_POST_XXX.
>
> Here is the link for the unbalanced cpu hotplug enable case:
> https://lkml.org/lkml/2016/5/6/61 .
>
> Thanks,
> Lianwei

Did anyone from the maintainer review the patch yet?

  reply	other threads:[~2016-06-07  5:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18  6:07 [PATCH v1] PM / sleep: make pm notifier called symmetrically Lianwei Wang
2016-05-18 20:34 ` Rafael J. Wysocki
2016-05-19  6:06   ` Lianwei Wang
2016-06-07  5:41     ` Lianwei Wang [this message]
2016-06-08  0:40       ` Rafael J. Wysocki
2016-06-10  6:47 Lianwei Wang
2016-06-10 14:00 ` Rafael J. Wysocki
2016-06-11  6:23   ` Lianwei Wang

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=CAJFUiJhKJT5W_fq_hMGSG7rCUU4dx9o-H5SLiYWmktem2faj1w@mail.gmail.com \
    --to=lianwei.wang@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).