dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Ilija Hadzic <ihadzic@research.bell-labs.com>
To: "Christian König" <deathsimple@vodafone.de>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/radeon: Disable dma rings for bo moves on r6xx
Date: Fri, 12 Jul 2013 09:23:20 -0500 (CDT)	[thread overview]
Message-ID: <Pine.GSO.4.64.1307120915460.13795@umail> (raw)
In-Reply-To: <51DFA7E9.2050102@vodafone.de>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1074 bytes --]



On Fri, 12 Jul 2013, Christian König wrote:

> Hi Ilija,
>
> well that's very interesting and no it's quite unlikely that this is cause by 
> the DMA ring because the radeon_sa_bo structure should be allocated on system 
> memory and the GPU can usually only access it if you map it through GART.
>

OK that's good information to know. I'll do some more investigation on my 
end.

> Is that easily reproducible for you? Is there already an open bugreport?
>

It typically happens out of the blue after several days of running, but 
it happens consistently (just like padding the radeon_sa_bo structure 
consistently suppresses the problem).

However, like I said, my kernel is full of my own patches that don't live 
in the upstream tree, so I am not excluding the possibility that one of my 
hacks introduced the problem (though, I find it unlikely).

I have not yet opened the bug report, because I first want to reproduce 
the problem with the upstream kernel that is free of my hacks. As soon as
I do that, I'll write the ticket.

-- Ilija

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2013-07-12 14:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11 19:35 [PATCH 1/3] drm/radeon: Disable dma rings for bo moves on r6xx alexdeucher
2013-07-11 19:35 ` [PATCH 2/3] drm/radeon: implement bo copy callback using CP DMA (v2) alexdeucher
2013-07-18 12:29   ` Marek Olšák
2013-07-11 19:35 ` [PATCH 3/3] drm/radeon: use CP DMA on r6xx for bo moves alexdeucher
2013-07-11 19:59 ` [PATCH 1/3] drm/radeon: Disable dma rings for bo moves on r6xx Ilija Hadzic
2013-07-11 20:05   ` Alex Deucher
2013-07-12  6:53   ` Christian König
2013-07-12 14:23     ` Ilija Hadzic [this message]
2013-07-12  6:50 ` Christian König
2013-07-12 13:04   ` 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=Pine.GSO.4.64.1307120915460.13795@umail \
    --to=ihadzic@research.bell-labs.com \
    --cc=alexander.deucher@amd.com \
    --cc=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).