public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Dave Airlie <airlied@gmail.com>,
	Keir Fraser <kier.fraser@eu.citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"iommu@lists.linux-foundation.org"
	<iommu@lists.linux-foundation.org>,
	Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [RFC] Make AGP work with IOMMU
Date: Mon, 3 Aug 2009 14:50:30 +0800	[thread overview]
Message-ID: <20090803065030.GA32461@zhen-devel.sh.intel.com> (raw)
In-Reply-To: <1248860205.19733.238.camel@macbook.infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]

On 2009.07.29 17:36:45 +0800, David Woodhouse wrote:
> On Wed, 2009-07-29 at 18:43 +1000, Dave Airlie wrote:
> > >> don't suppose we want page_to_gart or is the double function nicer?
> > >
> > > I pondered that briefly. But then observed that phys_to_gart() and
> > > gart_to_phys() _always_ describe an identity mapping, so perhaps they
> > > could just be ditched completely?
> > 
> > Yeah that could work too, no idea why they were introduced, well before my time.
> 
> http://git.infradead.org/users/dwmw2/iommu-agp.git?a=commitdiff;h=8bf2f3a9
> 
> It was introduced by Keir in 2005 for Xen (commit 07eee78e). I suspect
> it can die though, and that the right answer there is also to use the
> DMA API correctly.
> 

The commits on that tree looks fine to me. Thanks David! 
I've also done some testing on G45 here, I've also seen the write
faults before graphics device init or after dma unmap pages. I tried
to look it up in my memo, which turns out one message like this should
be a BIOS bug that doesn't initialize the GTT table correctly. But I'm
quite sure about it now, better to ask our chipset people to verify if
this problem has been fixed or not.

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-08-03  6:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-27 15:04 [RFC] Make AGP work with IOMMU David Woodhouse
2009-07-29  6:28 ` Dave Airlie
2009-07-29  7:15   ` David Woodhouse
2009-07-29  8:43     ` Dave Airlie
2009-07-29  9:01       ` David Woodhouse
2009-07-29  9:36       ` David Woodhouse
2009-08-03  6:50         ` Zhenyu Wang [this message]
2009-08-03  8:39           ` David Woodhouse
2009-08-04 23:52         ` [Xen-devel] " Jeremy Fitzhardinge
2009-08-05  6:44           ` David Woodhouse
2009-08-05  6:57             ` Dave Airlie
2009-08-05  7:08               ` David Woodhouse
2009-08-05 18:26               ` Jeremy Fitzhardinge
2009-08-05 23:12                 ` Dave Airlie
2009-08-06 19:32                   ` Jeremy Fitzhardinge
2009-08-06 19:36                     ` David Woodhouse

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=20090803065030.GA32461@zhen-devel.sh.intel.com \
    --to=zhenyuw@linux.intel.com \
    --cc=airlied@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=joerg.roedel@amd.com \
    --cc=kier.fraser@eu.citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xen-devel@lists.xensource.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