[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <451E40DF.30406@garzik.org>
Date: Sat, 30 Sep 2006 06:03:11 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Muli Ben-Yehuda <muli@...ibm.com>
CC: Andrew Morton <akpm@...l.org>, Greg KH <greg@...ah.com>,
Jim Paradis <jparadis@...hat.com>, Andi Kleen <ak@...e.de>,
LKML <linux-kernel@...r.kernel.org>, jdmason@...zu.us
Subject: Re: [PATCH] x86[-64] PCI domain support
Muli Ben-Yehuda wrote:
> On Fri, Sep 29, 2006 at 02:31:16AM +0300, Muli Ben-Yehuda wrote:
>> On Thu, Sep 28, 2006 at 07:03:28PM -0400, Jeff Garzik wrote:
>>
>>> hmmmm. What kernels did you test?
>> mainline as of today + several unrelated Calgary patches I'll post
>> shortly + your PCI domains patch + my Calgary patch. I'll test with
>> iommu=off next.
>>
>>> That should narrow down the problems. A problem with aic94xx sorta
>>> sounds like something unrelated.
>> Not necessarily - Calgary is an isolating IOMMU, meaning that if we
>> set up a mapping for aic94xx in the wrong IO space due to a Calgary
>> bug, aic94xx will fall over and die. Usually however this happens a
>> lot sooner. Also, we have code in Calgary to detect when an errant DMA
>> happens and it hasn't triggered in this case.
>
> Ok, turns out it's neither a PCI domains nor Calgary issue, since I
> can reproduce it on mainline with iommu=off. Must be an aic94xx
> issue, I'll send the details to linux-scsi in a bit.
Would you also make sure that Andrew has the necessary bits to keep
Calgary going under PCI domains? If it's a patch that sits on top of
linux-2.6.git + my patch, I can merge it into misc-2.6.git#pciseg (which
automatically goes into -mm). Otherwise, make sure -mm has the stack of
patches necessary.
Jeff
-
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