[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-8447b360a3897bdfb0677107564d1dd9ab6e63be@git.kernel.org>
Date: Fri, 12 Mar 2010 09:54:58 GMT
From: tip-bot for Jack Steiner <steiner@....com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
steiner@....com, tglx@...utronix.de, mingo@...e.hu
Subject: [tip:x86/urgent] x86, UV: Fix target_cpus() in x2apic_uv_x.c
Commit-ID: 8447b360a3897bdfb0677107564d1dd9ab6e63be
Gitweb: http://git.kernel.org/tip/8447b360a3897bdfb0677107564d1dd9ab6e63be
Author: Jack Steiner <steiner@....com>
AuthorDate: Thu, 11 Mar 2010 12:43:29 -0600
Committer: Ingo Molnar <mingo@...e.hu>
CommitDate: Fri, 12 Mar 2010 10:19:29 +0100
x86, UV: Fix target_cpus() in x2apic_uv_x.c
target_cpu() should initially target all cpus, not just cpu 0.
Otherwise systems with lots of disks can exhaust the interrupt
vectors on cpu 0 if a large number of disks are discovered
before the irq balancer is running.
Note: UV code only...
Signed-off-by: Jack Steiner <steiner@....com>
LKML-Reference: <20100311184328.GA21433@....com>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
arch/x86/kernel/apic/x2apic_uv_x.c | 4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kernel/apic/x2apic_uv_x.c b/arch/x86/kernel/apic/x2apic_uv_x.c
index 21db3cb..af0ca80 100644
--- a/arch/x86/kernel/apic/x2apic_uv_x.c
+++ b/arch/x86/kernel/apic/x2apic_uv_x.c
@@ -114,11 +114,9 @@ EXPORT_SYMBOL_GPL(uv_possible_blades);
unsigned long sn_rtc_cycles_per_second;
EXPORT_SYMBOL(sn_rtc_cycles_per_second);
-/* Start with all IRQs pointing to boot CPU. IRQ balancing will shift them. */
-
static const struct cpumask *uv_target_cpus(void)
{
- return cpumask_of(0);
+ return cpu_online_mask;
}
static void uv_vector_allocation_domain(int cpu, struct cpumask *retmask)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists