From: Andi Kleen <andi@firstfloor.org>
To: Daniel Haid <d.haid@gogi.tv>
Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
linux-kernel@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
alexdeucher@gmail.com, airlied@redhat.com
Subject: Re: Question about iommu on x86_64 and radeon driver.
Date: Wed, 1 Jun 2011 23:51:38 +0200 [thread overview]
Message-ID: <20110601215138.GG27166@one.firstfloor.org> (raw)
In-Reply-To: <21491fcfb013e21177140326efc0ee66@admin.gogi.tv>
On Wed, Jun 01, 2011 at 05:10:44PM +0100, Daniel Haid wrote:
> >Look in the source code. I somehow assumed it would activate it
> >but maybe it isn't. And the problem you have is related to
> >something else?
>
> If I have read the code correctly the only way to get
> swiotlb_force=1 in lib/swiotlb.c is to add the "swiotlb=force"
> argument to the kernel parameters.
>
> Without it on VIA chipsets swiotlb gets activated, but with
> swiotlb_force=0. In this case DMA to addresses below 4GB should be
> direct.
>
> But since I still get the error the radeon driver must (incorrectly)
> allocate memory above 4GB somewhere, but where?
Someone has to debug it. grep for the error message, read the
surrounding code, add printks, run it, until you figure out which allocation
has the problem.
Adding some radeon driver people to cc. The original problem
is described in http://choon.net/forum/read.php?21,106131,115940
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2011-06-01 21:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 21:56 Question about iommu on x86_64 and radeon driver Daniel Haid
2011-05-23 22:05 ` Konrad Rzeszutek Wilk
2011-05-23 23:45 ` Daniel Haid
2011-05-24 15:50 ` Konrad Rzeszutek Wilk
2011-05-24 21:33 ` Daniel Haid
2011-05-25 12:58 ` Konrad Rzeszutek Wilk
2011-05-25 14:28 ` Daniel Haid
2011-05-24 22:48 ` Andi Kleen
2011-05-25 10:00 ` Daniel Haid
2011-05-25 12:57 ` Konrad Rzeszutek Wilk
2011-05-25 14:51 ` Daniel Haid
2011-05-25 20:21 ` Daniel Haid
2011-05-25 23:05 ` Andi Kleen
2011-05-27 15:48 ` Daniel Haid
2011-05-27 15:55 ` Konrad Rzeszutek Wilk
2011-05-27 22:20 ` Daniel Haid
2011-05-31 13:45 ` Konrad Rzeszutek Wilk
2011-05-31 15:34 ` Daniel Haid
2011-05-31 16:02 ` Konrad Rzeszutek Wilk
[not found] ` <0a8cb4bcad7fcf091a6bbe158323bba0@admin.gogi.tv>
2011-05-31 16:20 ` Daniel Haid
[not found] ` <20110531190412.GA21245@dumpdata.com>
2011-05-31 19:57 ` Daniel Haid
2011-06-01 13:24 ` Konrad Rzeszutek Wilk
2011-06-01 16:10 ` Daniel Haid
2011-06-01 21:51 ` Andi Kleen [this message]
2011-06-01 21:58 ` Daniel Haid
2011-06-01 22:22 ` Andi Kleen
2011-06-03 17:31 ` [PATCH] tentative fix for radeon on systems >4GB without hardware iommu Daniel Haid
2011-06-03 20:44 ` Alex Deucher
2011-06-03 23:13 ` Konrad Rzeszutek Wilk
2011-06-06 17:45 ` Daniel Haid
2011-06-06 17:41 ` Daniel Haid
2011-06-06 19:08 ` Alex Deucher
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=20110601215138.GG27166@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=airlied@redhat.com \
--cc=alexdeucher@gmail.com \
--cc=d.haid@gogi.tv \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.