public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: Muli Ben-Yehuda <mulix@mulix.org>, Jon Mason <jdmason@us.ibm.com>,
	Linux-Kernel <linux-kernel@vger.kernel.org>,
	discuss@x86-64.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/3] x86-64: Calgary IOMMU - Calgary specific bits
Date: Thu, 23 Mar 2006 22:52:01 +0100	[thread overview]
Message-ID: <200603232252.02014.ak@suse.de> (raw)
In-Reply-To: <20060323214507.GE25830@rhun.haifa.ibm.com>

On Thursday 23 March 2006 22:45, Muli Ben-Yehuda wrote:
> On Thu, Mar 23, 2006 at 09:03:34PM +0200, Muli Ben-Yehuda wrote:
> 
> > > > X works :-) 
> > > 
> > > So it's behind a bridge that doesn't have an IOMMU?
> > 
> > No, it's behind a bridge that does have an IOMMU and is running with
> > translation enabled (it's on PHB 0 on this machine). I guess you are
> > concerned with userspace access to the graphics controller directly,
> > without a kernel driver having set up mapping previously? I will look
> > into it but emprirically X works so either userspace is not triggering
> > DMAs or the mappings have been set up by a driver.
> 
> Turns out that X does work on my machine (SLES 9SP2) but dies with a
> bad translation error on Jon's machine, which is otherwise identical
> except it runs gentoo. We are thinking how to best address this (add
> IOMMU aware drivers to X? *shudder*), but will disable translation by
> default on PHB 0 in the mean time for a friendlier user
> experience.

You could just enable it for mmaps on /dev/mem. 

-Andi


      reply	other threads:[~2006-03-23 21:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20  8:48 [PATCH 1/3] x86-64: Calgary IOMMU - introduce iommu_detected Muli Ben-Yehuda
2006-03-20  8:54 ` [PATCH 2/3] x86-64: Calgary IOMMU - Calgary specific bits Muli Ben-Yehuda
2006-03-20  8:56   ` [PATCH 3/3] x86-64: Calgary IOMMU - hook it in Muli Ben-Yehuda
2006-03-23 16:36     ` Andi Kleen
2006-03-23 17:30       ` Jon Mason
2006-03-23 17:48         ` Andi Kleen
2006-03-23 18:58           ` Jon Mason
2006-03-24  3:23       ` Muli Ben-Yehuda
2006-03-23 16:31   ` [PATCH 2/3] x86-64: Calgary IOMMU - Calgary specific bits Andi Kleen
2006-03-23 17:53     ` Muli Ben-Yehuda
2006-03-23 18:02       ` Andi Kleen
2006-03-23 19:03         ` Muli Ben-Yehuda
2006-03-23 21:45           ` Muli Ben-Yehuda
2006-03-23 21:52             ` Andi Kleen [this message]

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=200603232252.02014.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=discuss@x86-64.org \
    --cc=jdmason@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=mulix@mulix.org \
    /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