mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Enrico Mioso <mrkiko.rs@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Peter Zijlstra <peterz@infradead.org>,
	Anna-Maria Gleixner <anna-maria@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: CPU Hotplugging disabled, still cpuhp/%d threads running in my 32-bit system
Date: Wed, 11 Jan 2017 14:08:49 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.20.1701111408230.7486@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.20.1701111011210.3579@nanos>

Thank you very much Thomas, really.
Enrico


Enrico Mioso
Mobile Phone Number: +393807096934 ( +Telegram :) )
My Tox ID is: 7C593F402A3C8632D87AB4B948D492294C39A6A614464ECF843CA3429FB023284180472C7475

I like / recommend the usage of open messaging standards.

On Wed, 11 Jan 2017, Thomas Gleixner wrote:

> Date: Wed, 11 Jan 2017 10:16:10
> From: Thomas Gleixner <tglx@linutronix.de>
> To: Enrico Mioso <mrkiko.rs@gmail.com>
> Cc: linux-kernel@vger.kernel.org,
>     Boris Ostrovsky <boris.ostrovsky@oracle.com>,
>     Rasmus Villemoes <linux@rasmusvillemoes.dk>,
>     Peter Zijlstra <peterz@infradead.org>,
>     Anna-Maria Gleixner <anna-maria@linutronix.de>,
>     Ingo Molnar <mingo@kernel.org>,
>     Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> Subject: Re: CPU Hotplugging disabled,
>     still cpuhp/%d threads running in my 32-bit system
> 
> 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
>

      reply	other threads:[~2017-01-11 13:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10 22:32 Enrico Mioso
2017-01-11  9:16 ` Thomas Gleixner
2017-01-11 13:08   ` Enrico Mioso [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.20.1701111408230.7486@localhost.localdomain \
    --to=mrkiko.rs@gmail.com \
    --cc=anna-maria@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=boris.ostrovsky@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®