dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Ivanov <gnidorah@p0n4ik.tk>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: drm/radeon: "ring test failed" on PA-RISC Linux
Date: Tue, 17 Sep 2013 13:23:48 +0400	[thread overview]
Message-ID: <143321379409828@web24h.yandex.ru> (raw)
In-Reply-To: <20130910132529.GF5038@phenom.dumpdata.com>

Alex,

10.09.2013, в 16:37, Alex Deucher <alexdeucher@gmail.com> написал(а):

> The dummy page isn't really going to help much.  That page is just
> used as a safety placeholder for gart entries that aren't mapped on
> the GPU.  TTM (drivers/gpu/drm/ttm) actually does the allocation of
> the backing pages for the gart.  

> You may want to look there.

Ah, sorry. Indeed. Though, my idea with:

On Tue, Sep 10, 2013 at 5:20 AM, Alex Ivanov <gnidorah@p0n4ik.tk> wrote:

> Thanks! I'll try. Meanwhile i've tried a switch from page_alloc() to
> dma_alloc_coherent() in radeon_dummy_page_*(), which didn't help :(

doesn't make a sense at TTM part as well.

Konrad,

10.09.2013, 17:25, "Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>:
>
> Is this platform enabling the SWIOTLB layer? 

Doesn't look like. 

> The reason I am asking is
> b/c if you do indeed enable it you end up using the TTM DMA pool
> which allocates pages using the dma_alloc_coherent - which means that
> all of the pages that come out of TTM are already 'DMA' mapped.
>
> And that means the radeon_gart_bind and all its friends
> use the DMA addresses that have been constructed by SWIOTLB IOMMU.
>
> Perhaps the PA-RISC IOMMU creates the DMA addresses differently?
>
> When the card gets programmed, you do end up using ttm_agp_bind right?
> I am wondering if something like this:
>
> https://lkml.org/lkml/2010/12/6/512
>
> is needed to pass in the right DMA address?

No idea how to modify ttm_agp_bind() this way, though doesn't matter if
swiotlb isn't used anyway?
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2013-09-17  9:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <995101375614033@web11d.yandex.ru>
2013-09-09 16:44 ` drm/radeon: "ring test failed" on PA-RISC Linux Alex Ivanov
2013-09-09 17:43   ` Alex Deucher
2013-09-10  9:20     ` Alex Ivanov
2013-09-10 12:37       ` Alex Deucher
2013-09-10 13:03         ` Hans Verkuil
2013-09-10 13:25       ` Konrad Rzeszutek Wilk
2013-09-17  9:23         ` Alex Ivanov [this message]
2013-09-17 14:24           ` Alex Deucher
2013-09-17 19:33             ` Alex Ivanov
2013-09-20  6:52               ` Alex Ivanov
2013-09-20 21:27               ` Alex Deucher
2013-09-21  3:39                 ` Alex Ivanov
2013-09-23 20:11                   ` Konrad Rzeszutek Wilk
2013-09-25 16:29                     ` Alex Ivanov
2013-09-25 17:28                       ` Konrad Rzeszutek Wilk
2013-09-25 18:17                         ` Alex Deucher
2013-09-25 18:51                         ` Alex Ivanov
2013-09-26  8:39                           ` Alex Ivanov
2013-09-10 15:45   ` Michel Dänzer

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=143321379409828@web24h.yandex.ru \
    --to=gnidorah@p0n4ik.tk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=konrad.wilk@oracle.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