From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@gmail.com>,
Waldemar Rymarkiewicz <waldemarx.rymarkiewicz@intel.com>,
linux-pm@vger.kernel.org, Viresh Kumar <vireshk@kernel.org>,
Nishanth Menon <nm@ti.com>, Stephen Boyd <sboyd@codeaurora.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH v4 1/1] PM / OPP: Fix get sharing cpus when hotplug is used
Date: Thu, 27 Jul 2017 09:13:51 +0530 [thread overview]
Message-ID: <20170727034351.GF352@vireshk-i7> (raw)
In-Reply-To: <592bc7b8-615d-5d80-f328-eabdfe6c3828@arm.com>
On 26-07-17, 15:08, Sudeep Holla wrote:
> CPUs won't be unregistered on hotplug path
You sure? I don't you will get confused with this as you already know
all this, but I will still write it down for the sake of clarity.
We aren't talking about offlining a CPU here, but a real physical
hotplug. Why should the kernel keep a device structure for a device if
it isn't physically present on the system?
acpi_processor_remove() removes the CPU device and I thought it was
all related to that hotplug.
Am I missing something ?
> and hence I can't figure out
> why get_cpu_device would fail if all the CPUs were registered on boot.
> Just trying to understand the scenario and how it differs from normal
> hotplug case.
--
viresh
next prev parent reply other threads:[~2017-07-27 3:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-26 12:11 [PATCH v4 1/1] PM / OPP: Fix get sharing cpus when hotplug is used Waldemar Rymarkiewicz
2017-07-26 12:11 ` [PATCH v4 0/1] " Waldemar Rymarkiewicz
2017-07-26 13:10 ` [PATCH v4 1/1] PM / OPP: " Sudeep Holla
2017-07-26 13:54 ` Waldemar Rymarkiewicz
2017-07-26 14:08 ` Sudeep Holla
2017-07-26 14:41 ` Waldemar Rymarkiewicz
2017-07-26 15:20 ` Sudeep Holla
2017-07-27 3:43 ` Viresh Kumar [this message]
2017-07-27 0:03 ` Rafael J. Wysocki
2017-07-27 7:25 ` Waldemar Rymarkiewicz
2017-07-27 7:31 ` Viresh Kumar
2017-07-27 10:01 ` Waldemar Rymarkiewicz
2017-07-30 14:54 ` kbuild test robot
2017-07-31 11:14 ` Rafael J. Wysocki
2017-07-31 15:12 ` Waldemar Rymarkiewicz
2017-07-31 18:50 ` Rafael J. Wysocki
2017-08-01 4:37 ` Viresh Kumar
2017-08-01 11:53 ` Rafael J. Wysocki
2017-08-03 1:50 ` [kbuild-all] " Fengguang Wu
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=20170727034351.GF352@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=sudeep.holla@arm.com \
--cc=vireshk@kernel.org \
--cc=waldemar.rymarkiewicz@gmail.com \
--cc=waldemarx.rymarkiewicz@intel.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