mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Turquette <mturquette@ti.com>
To: linux-kernel@vger.kernel.org
Cc: linux-pm@lists.linux-foundation.org, linaro-dev@lists.linaro.org,
	patches@linaro.org, Mike Turquette <mturquette@ti.com>
Subject: [PATCH 2/2] cpu: update cpu_hotpluggable_mask in register_cpu
Date: Tue,  9 Aug 2011 18:33:27 -0700	[thread overview]
Message-ID: <1312940007-26069-3-git-send-email-mturquette@ti.com> (raw)
In-Reply-To: <1312940007-26069-1-git-send-email-mturquette@ti.com>

Update the cpu_hotpluggable_mask for each registered CPU which supports
hotplug.  This makes it trivial for kernel code to know which CPUs
support hotplug operations.

Signed-off-by: Mike Turquette <mturquette@ti.com>
---
 drivers/base/cpu.c |    4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
index 251acea..91ddcf8 100644
--- a/drivers/base/cpu.c
+++ b/drivers/base/cpu.c
@@ -224,8 +224,10 @@ int __cpuinit register_cpu(struct cpu *cpu, int num)
 
 	error = sysdev_register(&cpu->sysdev);
 
-	if (!error && cpu->hotpluggable)
+	if (!error && cpu->hotpluggable) {
 		register_cpu_control(cpu);
+		set_cpu_hotpluggable(num, true);
+	}
 	if (!error)
 		per_cpu(cpu_sys_devices, num) = &cpu->sysdev;
 	if (!error)
-- 
1.7.4.1


      parent reply	other threads:[~2011-08-10  1:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10  1:33 [PATCH 0/2] new cpumask for hotpluggable CPUs Mike Turquette
2011-08-10  1:33 ` [PATCH 1/2] cpumask: introduce " Mike Turquette
2011-08-10  2:01   ` Christian Robottom Reis
2011-08-10  2:03     ` Turquette, Mike
2011-08-10  8:42   ` Amit Kucheria
2011-08-10 17:25     ` Turquette, Mike
2011-08-10  1:33 ` Mike Turquette [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=1312940007-26069-3-git-send-email-mturquette@ti.com \
    --to=mturquette@ti.com \
    --cc=linaro-dev@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=patches@linaro.org \
    /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®