Date: Fri, 24 Oct 2008 16:18:18 -0700 (PDT)
Message-Id: <20081024.161818.256978293.davem@davemloft.net>
To: galak@kernel.crashing.org
Cc: csnook@redhat.com, maxk@qualcomm.com, linuxppc-dev@ozlabs.org,
       linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: default IRQ affinity change in v2.6.27 (breaking several SMP
 PPC based systems)
From: David Miller <davem@davemloft.net>
In-Reply-To: <36A821E7-7F37-42AF-9A05-7205FCBF89EE@kernel.crashing.org>
References: <4E3CD4D5-FC1B-40BF-A776-C612B95806B8@kernel.crashing.org>
	<4901E6FB.4070200@redhat.com>
	<36A821E7-7F37-42AF-9A05-7205FCBF89EE@kernel.crashing.org>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 790
Lines: 18

From: Kumar Gala <galak@kernel.crashing.org>
Date: Fri, 24 Oct 2008 10:39:05 -0500

> As for making it ARCH specific, that doesn't really help since not
> all PPC hw has the limitation I spoke of.  Not even all MPIC (in our
> cases) have the limitation.

Since the PPC code knows exactly which MPICs have the problem the
PPC code is where the constraining can occur.

I agree completely with the suggestion that the arch code has to
interpret the cpumask as appropriate for the hardware, since the
user can stick "illegal" values there anyways.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/