From: Mike Galbraith <bitbucket@online.de>
To: markh@compro.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: question about cpu_active_mask
Date: Wed, 18 Dec 2013 05:00:56 +0100 [thread overview]
Message-ID: <1387339256.5315.12.camel@marge.simpson.net> (raw)
In-Reply-To: <52B0BBBD.3000704@compro.net>
On Tue, 2013-12-17 at 16:01 -0500, Mark Hounschell wrote:
> I hope it is OK to ask a newbie question here. I'm trying to better
> understand the boot process. I can't seem to find where in the kernel
> sources the cpu_active_mask (defined in include/linux/cpumask.h) gets
> populated. I can see that it does get populated as it brings cpus online
> but it is not obvious to me where. I'm using a 32 bit 3.4.x flavor kernel.
Try git grep set_cpu_active.
-Mike
next prev parent reply other threads:[~2013-12-18 4:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 21:01 question about cpu_active_mask Mark Hounschell
2013-12-18 4:00 ` Mike Galbraith [this message]
[not found] ` <294848935.31685.1387339274917.JavaMail.root@mx2.compro.net>
2013-12-18 12:51 ` Mark Hounschell
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=1387339256.5315.12.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@compro.net \
/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