From: Sudeep Holla <sudeep.holla@arm.com>
To: Sumit Gupta <sumitg@nvidia.com>, linux-kernel@vger.kernel.org
Cc: gregkh@linuxfoundation.org, Sudeep Holla <sudeep.holla@arm.com>,
bbasu@nvidia.com, linux-tegra@vger.kernel.org
Subject: Re: [PATCH ] drivers/base: cacheinfo: remove warning in resume
Date: Tue, 30 Aug 2016 11:20:18 +0100 [thread overview]
Message-ID: <32ada52a-4d47-282a-ef10-33d3e32fbd52@arm.com> (raw)
In-Reply-To: <1472455254-27692-1-git-send-email-sumitg@nvidia.com>
Hi Sumit,
I understand the warning we get but the patch is completely wrong.
One it removes the feature of adding/removing the cache devices
on cpu hotplug events. Have you tested your patch with simple cpu
hotplug and seen no change before and after this change ?
On 29/08/16 08:20, Sumit Gupta wrote:
> CPU notifier is present for creating device
> entries for child node "cache" under parent
> node "cpu" as per DT.
Again DT is only on few architectures not on all(e.g. x86)
> During resume from
> suspend, while booting all non-boot CPU's,
> this notifier for adding cache device gets
> called before cpu device is added by
> device_resume. Because of this warning message
> of "parent should not be sleeping" comes during
> resume.
>
Yes that's correct and needs to be fixed. I have seen this but haven't
spent much time to check in detail. It's harmless warning IMO.
See the comment in the code too:"This is a fib. But we'll allow new
children to be added below a resumed device, even if the device hasn't
been completed yet"
CPU devices are special and they have separate hotplug paths. So we need
to consider that for cpu devices and set is_prepared quite early.
> Removing the notifier to explicitly add/remove
> cache device as CPU and cache device get
> added/removed anyway as part of normal suspend
> resume sequence.
> dpm_resume_end - > dpm_resume -> device_resume
>
Yes, but:
1. the caches objects are visible even when the cpu is offline
2. how is this handled for normal cpu-hotplug events ? This patch
breaks the existing feature.
> Signed-off-by: Sumit Gupta <sumitg@nvidia.com>
> ---
> drivers/base/cacheinfo.c | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/drivers/base/cacheinfo.c b/drivers/base/cacheinfo.c
> index e9fd32e91668..17d9c051a16f 100644
> --- a/drivers/base/cacheinfo.c
> +++ b/drivers/base/cacheinfo.c
> @@ -544,8 +544,6 @@ static int __init cacheinfo_sysfs_init(void)
> goto out;
> }
> }
> - __hotcpu_notifier(cacheinfo_cpu_callback, 0);
> -
> out:
> cpu_notifier_register_done();
> return rc;
>
--
Regards,
Sudeep
next prev parent reply other threads:[~2016-08-30 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-29 7:20 Sumit Gupta
2016-08-30 10:20 ` Sudeep Holla [this message]
2016-09-02 12:58 ` Sumit Gupta
2016-09-02 15:02 ` Sudeep Holla
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=32ada52a-4d47-282a-ef10-33d3e32fbd52@arm.com \
--to=sudeep.holla@arm.com \
--cc=bbasu@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=sumitg@nvidia.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
Powered by JetHome