On Fri, Feb 13, 2015 at 03:52:08PM +0000, Mark Rutland wrote: > > @@ -194,10 +195,6 @@ int __cpu_disable(void) > > unsigned int cpu = smp_processor_id(); > > int ret; > > > > - ret = platform_cpu_disable(cpu); > > - if (ret) > > - return ret; > > For PSCI 0.2+ I was hoping to hook the MIGRATE logic in here. The secure > side may reject hotplugging of a CPU, but it's a dynamic property of the > system and so can't be probed once at boot time.
You may have to think about how to deal with the static nature of the sysfs CPU hotplug properties then - or, you may wish to have the existing behaviour where we expose the sysfs hotplug properties on all CPUs and rely on returning -EPERM. One question does come up - if it's a dynamic property of the system, what ensures that it can't change between the point when we test it (in __cpu_disable()) and when we actually come to take the CPU offline? How does the secure side signal its rejection of hotunplugging of a CPU? If it happens after __cpu_disable(), then that's a problem: the system will have gone through all the expensive preparation by that time to shut the CPU down, and it will expect the CPU to go offline. The only way it can come back at that point is by going through a CPU plug-in cycle... which means going back through secondary_start_kernel. -- FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
