[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090507215933K.fujita.tomonori@lab.ntt.co.jp>
Date: Thu, 7 May 2009 21:59:19 +0900
From: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>
To: joerg.roedel@....com
Cc: dwmw2@...radead.org, fujita.tomonori@....ntt.co.jp,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
mingo@...hat.com, airlied@...ux.ie
Subject: Re: IOMMU and graphics cards
On Thu, 7 May 2009 14:15:35 +0200
Joerg Roedel <joerg.roedel@....com> wrote:
> On Thu, May 07, 2009 at 11:22:01AM +0100, David Woodhouse wrote:
> > On Thu, 2009-05-07 at 12:01 +0200, Joerg Roedel wrote:
> > > > Looks like the DRM code uses the DMA API.
> > >
> > > The proprietary drivers make problems so far. For the ATI one I am in
> > > contact with the developers to try to fix it. But I can't do anything
> > > about the other proprietary driver I am aware of :-(
> >
> > I see no harm in "breaking" code which was already broken. If that's the
> > only reason we're enabling the graphics workaround, let's turn it off.
>
> Well, it is not that simple. Having no workaround at all will not result
> in working proprietary drivers. More likely is that distros just disable
> the IOMMU because their customers want to use these drivers for working
> 3d acceleration.
Have you already discussed this issue with distribution people?
I'm not sure if they would just disable the IOMMU. They want it for
exotic virtualization features?
> As I wrote in the original mail I think we should just make sure that
> these drivers still work with an IOMMU without disabling device
> isolation.
--
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