From: Daniel Haid <d.haid@gogi.tv>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Question about iommu on x86_64 and radeon driver.
Date: Tue, 24 May 2011 00:45:47 +0100 [thread overview]
Message-ID: <756073831c36e0404199a4e8239bcb70@admin.gogi.tv> (raw)
In-Reply-To: <20110523220536.GB11961@dumpdata.com>
> There had to be more than 'Map around memory hole'? Was it called
> GART or IOMMU?
I do not think that there was "IOMMU" or "GART" written there,
but I do not think that the mainboard in question has an IOMMU
(Am I correct that it would be a feature of the mainboard while
the AMD GART is a feature of the CPU?).
I will look again as soon as I have physical access to the system.
> The problem you are hitting (I think) is that the AMD GART poor-man
> IOMMU is turned off
> and the SWIOTLB is used instead. If you would like some technical
> details, take a look at:
>
> http://lists.freedesktop.org/archives/dri-devel/2011-January/006885.html
> (the point #2 is what you are hitting).
You are correct. In all the cases where the radeon card does not work
I see that SWIOTLB has been enabled in the kernel log.
So this is a bug? I suppose that all hardware should be working with
SWIOTLB? Will a patch that fixes this somewhen be included?
(The bug where your link points to was closed with WONTFIX)
> Not sure why the AMD GART IOMMU gets disabled on VIA chipsets. You
> might
> want to use 'git gui blame arch/x86/kernel/early-quirks.c' and look
> at the code in question to figure that out.
> Well, if everything works.... but you might just want to use
> the git gui blame to take a look at the back-story of why the quirk
> was added.
Unfortunately I am getting crashes with "iommu=allowed". I will look
at git blame.
Thank you for your answers.
next prev parent reply other threads:[~2011-05-23 23:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 21:56 Daniel Haid
2011-05-23 22:05 ` Konrad Rzeszutek Wilk
2011-05-23 23:45 ` Daniel Haid [this message]
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
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=756073831c36e0404199a4e8239bcb70@admin.gogi.tv \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®