linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Abel Wu <abel.w@icloud.com>
Cc: rjw@rjwysocki.net, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, hewenliang4@huawei.com,
	wuyun.wu@huawei.com
Subject: Re: [PATCH] PM: hibernate: add sanity check on power_kobj
Date: Tue, 2 Feb 2021 10:04:52 +0100	[thread overview]
Message-ID: <20210202090451.GA27619@amd> (raw)
In-Reply-To: <F87648CF-E5D6-41C7-9F4E-87A4BA2A4786@icloud.com>

[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]

On Tue 2021-02-02 09:59:11, Abel Wu wrote:
> 
> 
> > On Feb 1, 2021, at 6:52 PM, Pavel Machek <pavel@ucw.cz> wrote:
> > 
> > On Mon 2021-02-01 02:50:41, Abel Wu wrote:
> >> The @power_kobj is initialized in pm_init() which is the same
> >> initcall level as pm_disk_init(). Although this dependency is
> >> guaranteed based on the current initcall serial execution model,
> >> it would still be better do a cost-less sanity check to avoid
> >> oops once the dependency is broken.
> > 
> > I don't believe this is good idea. If the dependency is ever broken,
> > this will make failure more subtle and harder to debug.
> 
> Thanks for reviewing. I think the cmdline parameter initcall_debug will
> help in this case.
> Actually we are trying to make initcalls being called asynchronously to
> reduce boot time which is crucial to our cloud-native business. And we
> resolve this kind of dependencies by retrying failed initcalls.

And this patch is okay if that gets mainlined, but not before.

Best regards,
							Pavel
							
-- 
http://www.livejournal.com/~pavelmachek

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

      reply	other threads:[~2021-02-02  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01  7:50 [PATCH] PM: hibernate: add sanity check on power_kobj Abel Wu
2021-02-01 10:52 ` Pavel Machek
2021-02-02  1:59   ` Abel Wu
2021-02-02  9:04     ` Pavel Machek [this message]

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=20210202090451.GA27619@amd \
    --to=pavel@ucw.cz \
    --cc=abel.w@icloud.com \
    --cc=hewenliang4@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=wuyun.wu@huawei.com \
    /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).