Rafael, On Sat, 27 Feb 2016, Rafael J. Wysocki wrote: > Say we've taken all of them offline and now we are ready to eject. If an > online from sysfs (or any other place) comes in at this point, we'll be > ejecting a CPU that's potentially doing something which is not awesome. > > That's why we have device_hotplug_lock and some ugly code related to it. > > It extends to parents and children somewhat because of device objects > representing packages (we want those to be "offline" only if all their > children are offline) and that's why the lock is held around offline from > sysfs too. > > I'm not entirely happy with this for quite obvious reasons, but it gets > the job done ATM. Understood. I'll fix that thing up so that won't happen and I put it on the list of things to look at deeper. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
