[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20070524.234031.78709215.davem@davemloft.net>
Date: Thu, 24 May 2007 23:40:31 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: michael@...erman.id.au
Cc: ebiederm@...ssion.com, gregkh@...e.de, jacliburn@...lsouth.net,
ninex@...eX.eu.org, akpm@...ux-foundation.org, ak@...e.de,
ninex@...pl, linux-kernel@...r.kernel.org,
linux-pci@...ey.karlin.mff.cuni.cz, tony.luck@...el.com
Subject: Re: [PATCH 1/2] msi: Invert the sense of the MSI enables.
From: Michael Ellerman <michael@...erman.id.au>
Date: Fri, 25 May 2007 15:14:10 +1000
> On Thu, 2007-05-24 at 22:19 -0600, Eric W. Biederman wrote:
> > Currently we blacklist known bad msi configurations which means we
> > keep getting MSI enabled on chipsets that either do not support MSI,
> > or MSI is implemented improperly. Since the normal IRQ routing
> > mechanism seems to works even when MSI does not, this is a bad default
> > and causes non-functioning systems for no good reason.
> >
> > So this patch inverts the sense of the MSI bus flag to only enable
> > MSI on known good systems. I am seeding that list with the set of
> > chipsets with an enabled hypertransport MSI mapping capability. Which
> > is as close as I can come to an generic MSI enable. So for actually
> > using MSI this patch is a regression, but for just having MSI enabled
> > in the kernel by default things should just work with this patch
> > applied.
>
> I guess this is a good idea for random x86 machines. On powerpc I think
> we'll just turn it on for every bus, and let the existing per-platform
> logic decide.
I think I'll turn it on always on sparc64.
-
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