From: Li Zhong <zhong@linux.vnet.ibm.com>
To: Tejun Heo <tj@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
gregkh@linuxfoundation.org, rafael.j.wysocki@intel.com,
toshi.kani@hp.com
Subject: Re: [RFC PATCH v5 1/2] Use lock_device_hotplug() in cpu_probe_store() and cpu_release_store()
Date: Wed, 23 Apr 2014 10:00:26 +0800 [thread overview]
Message-ID: <1398218426.2805.42.camel@ThinkPad-T5421.cn.ibm.com> (raw)
In-Reply-To: <20140422204006.GA3615@mtj.dyndns.org>
On Tue, 2014-04-22 at 16:40 -0400, Tejun Heo wrote:
> Hello,
>
> On Tue, Apr 22, 2014 at 10:29:37AM +0800, Li Zhong wrote:
> > The probe/release files are attribute files for cpu subsys, looks like
> > following in sysfs dirs
> >
> > $ cd /sys/devices/system/cpu/
> > $ ls -l
> > total 0
> > drwxr-xr-x. 7 root root 0 Apr 17 19:00 cpu0
> > drwxr-xr-x. 4 root root 0 Apr 17 19:00 cpu1
> > drwxr-xr-x. 4 root root 0 Apr 17 19:00 cpu10
> > ......
> > drwxr-xr-x. 3 root root 0 Apr 20 08:00 cpufreq
> > drwxr-xr-x. 2 root root 0 Apr 20 08:00 cpuidle
> > -rw-------. 1 root root 65536 Apr 21 00:28 dscr_default
> > -r--r--r--. 1 root root 65536 Apr 21 00:28 kernel_max
> > -r--r--r--. 1 root root 65536 Apr 21 00:28 offline
> > -r--r--r--. 1 root root 65536 Sep 4 2014 online
> > -r--r--r--. 1 root root 65536 Apr 21 00:28 possible
> > drwxr-xr-x. 2 root root 0 Apr 20 08:00 power
> > -r--r--r--. 1 root root 65536 Apr 17 20:46 present
> > --w-------. 1 root root 65536 Apr 21 00:28 probe <-----
> > --w-------. 1 root root 65536 Apr 21 00:28 release <-----
> > -rw-------. 1 root root 65536 Apr 21 00:28 subcores_per_core
> > -rw-r--r--. 1 root root 65536 Apr 21 00:28 uevent
> >
> > From the code, it seems cpu subsys won't be unregistered, and it doesn't
> > make sense to remove all the cpus in the system.
>
> I don't think I'm following you. Are you saying that no files which
> are protected under the hotplug lock that cpu subsys uses are removed
> during offlining?
Sorry, Maybe I didn't say it clearly.
There are files under cpu#, e.g.
$ cd /sys/devices/system/cpu/cpu0
$ ls
cache dscr node1 pmc1 pmc5 smt_snooze_delay
uevent
cpuidle mmcr0 online pmc2 pmc6 spurr
crash_notes mmcr1 physical_id pmc3 power subsystem
crash_notes_size mmcra pir pmc4 purr topology
If you remove cpu0, then the cpu0 directory will be removed, together
with the "online" file in the directory, while some other process might
be writing 0 or 1 to it.
But here, for the probe/release, take "release" for example, if user
writes something that stands for cpu0 to it, the cpu0 will be removed,
and the cpu0 directory and the files under it will be removed. But
"release" itself is not removed.
They are attributes of cpu_subsys, not of some specific cpus.
Hopes the above makes things a bit clearer.
Thanks, Zhong
>
> Thanks.
>
next prev parent reply other threads:[~2014-04-23 2:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 9:18 [RFC PATCH] Suppress a device hot remove related lockdep warning Li Zhong
2014-04-10 13:31 ` Tejun Heo
2014-04-11 4:10 ` [RFC PATCH v2] Use kernfs_break_active_protection() for device online store callbacks Li Zhong
2014-04-11 10:26 ` Tejun Heo
2014-04-14 7:47 ` [RFC PATCH v3] " Li Zhong
2014-04-14 20:13 ` Tejun Heo
2014-04-15 2:44 ` Li Zhong
2014-04-15 14:50 ` Tejun Heo
2014-04-16 1:41 ` Li Zhong
2014-04-16 15:17 ` Tejun Heo
2014-04-17 3:05 ` Li Zhong
2014-04-17 15:06 ` Tejun Heo
2014-04-17 6:50 ` [RFC PATCH v4] " Li Zhong
2014-04-17 15:17 ` Tejun Heo
2014-04-18 8:33 ` Li Zhong
2014-04-21 9:20 ` [RFC PATCH v5 1/2] Use lock_device_hotplug() in cpu_probe_store() and cpu_release_store() Li Zhong
2014-04-21 9:23 ` [RFC PATCH v5 2/2] Use kernfs_break_active_protection() for device online store callbacks Li Zhong
2014-04-21 22:46 ` Tejun Heo
2014-04-22 3:34 ` Li Zhong
2014-04-22 10:11 ` Rafael J. Wysocki
2014-04-23 1:50 ` Li Zhong
2014-04-23 10:54 ` Rafael J. Wysocki
2014-04-24 1:13 ` Li Zhong
2014-04-22 20:44 ` Tejun Heo
2014-04-22 22:21 ` Rafael J. Wysocki
2014-04-23 14:23 ` Tejun Heo
2014-04-23 16:12 ` Rafael J. Wysocki
2014-04-23 16:52 ` Tejun Heo
2014-04-24 8:59 ` Li Zhong
2014-04-24 10:02 ` Rafael J. Wysocki
2014-04-25 1:46 ` Li Zhong
2014-04-25 12:47 ` Rafael J. Wysocki
2014-04-28 1:49 ` Li Zhong
2014-04-23 5:03 ` Li Zhong
2014-04-23 10:58 ` Rafael J. Wysocki
2014-04-24 1:33 ` Li Zhong
2014-05-09 8:35 ` Li Zhong
2014-05-09 8:40 ` [RFC PATCH v6 1/2 ] Use lock_device_hotplug() in cpu_probe_store() and cpu_release_store() Li Zhong
2014-05-09 8:40 ` [RFC PATCH v6 2/2] Implement lock_device_hotplug_sysfs() by breaking active protection Li Zhong
2014-04-21 22:38 ` [RFC PATCH v5 1/2] Use lock_device_hotplug() in cpu_probe_store() and cpu_release_store() Tejun Heo
2014-04-22 2:29 ` Li Zhong
2014-04-22 20:40 ` Tejun Heo
2014-04-23 2:00 ` Li Zhong [this message]
2014-04-23 14:39 ` Tejun Heo
2014-04-24 8:37 ` Li Zhong
2014-04-24 14:32 ` Tejun Heo
2014-04-25 1:56 ` Li Zhong
2014-04-25 12:28 ` Tejun Heo
2014-04-28 0:51 ` Li Zhong
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=1398218426.2805.42.camel@ThinkPad-T5421.cn.ibm.com \
--to=zhong@linux.vnet.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=tj@kernel.org \
--cc=toshi.kani@hp.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
all inboxes | Powered by JetHome®