From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754132AbcL0LVS (ORCPT ); Tue, 27 Dec 2016 06:21:18 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:40892 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753450AbcL0LVH (ORCPT ); Tue, 27 Dec 2016 06:21:07 -0500 Date: Tue, 27 Dec 2016 12:17:54 +0100 (CET) From: Thomas Gleixner To: Sam Ravnborg cc: LKML , Sebastian Siewior , Ingo Molnar , Peter Zijlstra Subject: Re: [patch 00/10] cpu/hotplug: Final cleanup In-Reply-To: <20161222175923.GB17658@ravnborg.org> Message-ID: References: <20161221191947.089046759@linutronix.de> <20161222175923.GB17658@ravnborg.org> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 22 Dec 2016, Sam Ravnborg wrote: > Hi Thomas. > > On Wed, Dec 21, 2016 at 08:19:47PM +0100, Thomas Gleixner wrote: > > The following series completes the cpuhotplug rework stage ONE. > > Just curious - what is the stage TWO (and onwards) plan? > lwn had some coverage of this work but I assume the > article is somewhat outdated. Stage 2 is to consolidate all the archictecture code, i.e. reduce it to really arch specific callbacks and keep all the other things (synchronization, state settings etc.) in the core code. After that we can do smart things like speed up the boot hotplug process: prepare CPU1 kick CPU1 prepare CPU2 kick CPU2 .... prepare CPUN kick CPUN check CPU1 alive bringup CPU1 ... check CPUN alive bringup CPUN That saves ~200ms per CPU on x86, which we now spend busy waiting for the CPU to come alive. There is more stuff which we can do in the long run like synchrounosly letting CPUs bring up themself after the basic init/sync checks, but that needs lot of surgery all over the place. Thanks, tglx