From: Joerg Roedel <joro@8bytes.org>
To: David Miller <davem@davemloft.net>
Cc: dwmw2@infradead.org, airlied@linux.ie,
linux-kernel@vger.kernel.org, fujita.tomonori@lab.ntt.co.jp,
iommu@lists.linux-foundation.org, mingo@redhat.com
Subject: Re: IOMMU and graphics cards
Date: Fri, 8 May 2009 11:35:27 +0200 [thread overview]
Message-ID: <20090508093526.GB13708@8bytes.org> (raw)
In-Reply-To: <20090507.113632.210373283.davem@davemloft.net>
On Thu, May 07, 2009 at 11:36:32AM -0700, David Miller wrote:
> From: David Woodhouse <dwmw2@infradead.org>
> Date: Thu, 07 May 2009 11:22:01 +0100
>
> > 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.
>
> Seriously, this is an enormous price to pay just for one bad apple
> proprietary driver.
>
> I can't believe the level of concessions some people are suggesting.
This concession is already in the VT-d code. And this concession is
_enabled_ in enterprise distribtions supporting VT-d. I don't like the
way it is implemented there and I definitly will not implement a similar
way for the AMD IOMMU. What I try to achieve is a consistent solution
for both IOMMUs. Having the broken drivers work on VT-d but not on
AMD IOMMU is clearly a bad solution.
The other way to achieve consistency is to remove the workaround from
VT-d code which significantly increases the chance to get the broken
stuff fixed. David?
> Let's not make IOMMU's basically useless by working around one broken
> driver.
Agreed.
> Proper interfaces for what this driver is trying to do have existed in
> the kernel for 10+ years. There are no excuses, and it's time for
> Nvidia to get with the game plan.
Agreed.
Joerg
next prev parent reply other threads:[~2009-05-08 9:35 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-28 15:05 IOMMU and graphics cards Joerg Roedel
2009-04-28 15:28 ` David Woodhouse
2009-04-28 16:04 ` Joerg Roedel
2009-05-07 7:47 ` FUJITA Tomonori
2009-05-07 10:01 ` Joerg Roedel
2009-05-07 10:22 ` David Woodhouse
2009-05-07 10:42 ` FUJITA Tomonori
2009-05-07 12:15 ` Joerg Roedel
2009-05-07 12:59 ` FUJITA Tomonori
2009-05-07 14:37 ` Joerg Roedel
2009-05-07 17:04 ` Christoph Hellwig
2009-05-07 18:36 ` David Miller
2009-05-08 9:35 ` Joerg Roedel [this message]
2009-07-06 12:26 ` David Woodhouse
2009-07-06 13:11 ` Joerg Roedel
2009-07-06 14:18 ` David Woodhouse
2009-07-06 21:35 ` Dave Airlie
2009-07-06 22:00 ` Dave Airlie
2009-07-07 8:54 ` Joerg Roedel
2009-07-07 15:24 ` Duran, Leo
2009-07-07 15:33 ` Duran, Leo
2009-07-07 15:36 ` David Woodhouse
2009-07-07 8:59 ` Joerg Roedel
2009-07-07 9:16 ` David Woodhouse
2009-07-07 9:05 ` David Woodhouse
2009-05-07 10:23 ` FUJITA Tomonori
2009-05-07 11:01 ` Ingo Molnar
2009-05-07 11:14 ` FUJITA Tomonori
2009-05-07 11:26 ` Ingo Molnar
2009-05-07 12:00 ` Joerg Roedel
2009-05-07 10:55 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090508093526.GB13708@8bytes.org \
--to=joro@8bytes.org \
--cc=airlied@linux.ie \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox