Re: [patch 18/20] cpu/hotplug: Let upcoming cpu bring itself fully up

On Fri, Feb 26, 2016 at 06:43:41PM -, Thomas Gleixner wrote: > @@ -1204,7 +1212,7 @@ static bool cpuhp_is_ap_state(enum cpuhp > { > if (state >= CPUHP_AP_OFFLINE && state <= CPUHP_AP_ONLINE) > return true; FWIW, this test is superfluous after this change, because

Re: [patch 18/20] cpu/hotplug: Let upcoming cpu bring itself fully up

On Fri, Feb 26, 2016 at 06:43:41PM -, Thomas Gleixner wrote: > @@ -1204,7 +1212,7 @@ static bool cpuhp_is_ap_state(enum cpuhp > { > if (state >= CPUHP_AP_OFFLINE && state <= CPUHP_AP_ONLINE) > return true; FWIW, this test is superfluous after this change, because

[patch 18/20] cpu/hotplug: Let upcoming cpu bring itself fully up

Let the upcoming cpu kick the hotplug thread and let itself complete the bringup. That way the controll side can just wait for the completion or later when we made the hotplug machinery async not care at all. Signed-off-by: Thomas Gleixner --- include/linux/cpuhotplug.h |

[patch 18/20] cpu/hotplug: Let upcoming cpu bring itself fully up

Let the upcoming cpu kick the hotplug thread and let itself complete the bringup. That way the controll side can just wait for the completion or later when we made the hotplug machinery async not care at all. Signed-off-by: Thomas Gleixner --- include/linux/cpuhotplug.h |9 --