From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762887AbdAKJQP (ORCPT ); Wed, 11 Jan 2017 04:16:15 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:57023 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751555AbdAKJQN (ORCPT ); Wed, 11 Jan 2017 04:16:13 -0500 Date: Wed, 11 Jan 2017 10:16:10 +0100 (CET) From: Thomas Gleixner To: Enrico Mioso cc: linux-kernel@vger.kernel.org, Boris Ostrovsky , Rasmus Villemoes , Peter Zijlstra , Anna-Maria Gleixner , Ingo Molnar , Sebastian Andrzej Siewior Subject: Re: CPU Hotplugging disabled, still cpuhp/%d threads running in my 32-bit system In-Reply-To: Message-ID: References: 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 Tue, 10 Jan 2017, Enrico Mioso wrote: > Hello guys. > I disabled CPU hotplugging in my .config: still I can see what follows in the > process list. > > 11 ? S 0:00 [cpuhp/0] > 12 ? S 0:00 [cpuhp/1] > > And from what I can see in kernel/cpu.c:574, this is related to CPU > hotplugging. > Is this normal? And, out of curiosity, why? Yes. We need the threads for bringing up the CPUs and for modules and other functionality to set up per cpu related things. The thread makes sure that the code runs on the CPUs and handles the functionality related to install/remove of hotplug callbacks. Thanks, tglx