[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080822070931.GY14110@elte.hu>
Date: Fri, 22 Aug 2008 09:09:31 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
joerg.roedel@....com, mingo@...hat.com, tglx@...utronix.de,
hpa@...or.com, linux-kernel@...r.kernel.org,
iommu@...ts.linux-foundation.org, muli@...ibm.com
Subject: Re: [PATCH 0/8] x86 dma_*_coherent rework patchset v2
* Jesse Barnes <jbarnes@...tuousgeek.org> wrote:
> > Surely, this patchset should be for 2.6.28.
> >
> > Can you send this via the x86 tree instead of pci?
> >
> > - IOMMU code is arch stuff rather than pci.
> > - We can avoid a mistake such as the previous one.
>
> Yeah I was thinking 2.6.28 too, via the x86 tree. The problem last
> time was that I sent it too soon (I misunderstood Ingo when he said it
> was ready) so we broke the build on some non-x86 platforms. I don't
> think that'll be an issue this time, but we may as well push through
> x86 anyway; I agree that IOMMU is really a platform feature more than
> a PCI one.
yeah, GART/IOMMU has been historically a more platform specific thing
although there's certainly no hard boundaries. This code will show up in
linux-next as well soon, so there's plenty of time to discover and fix
any cross-arch breakages. (if any)
and if the PCI tree becomes very active in this area that would make the
movement of these commits over there more practical we can do that too
at any point of time, it's all kept separate in tip/x86/iommu, purely
based on Linus's tree. The blessings of 160+ topic branches ;-)
Ingo
--
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