dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/4] drm/radeon: move ring syncing after bo validation
Date: Thu, 23 Feb 2012 19:27:34 +0100	[thread overview]
Message-ID: <4F468516.2010205@vodafone.de> (raw)
In-Reply-To: <CAH3drwaayhHk0cyK67mTdJNTC3Ox1GTPsELjGK9fqRtO9ODG2A@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1688 bytes --]

On 23.02.2012 18:32, Jerome Glisse wrote:
> 2012/2/23 Mathias Fröhlich <Mathias.Froehlich@gmx.net 
> <mailto:Mathias.Froehlich@gmx.net>>
>
>
>     Christian,
>
>     On Thursday, February 23, 2012 15:18:42 Christian König wrote:
>     > The function radeon_bo_list_validate can cause a
>     > bo to move, resulting in a different sync_obj
>     > and a dependency to wait for this move to finish.
>     >
>     > Signed-off-by: Christian König <deathsimple@vodafone.de
>     <mailto:deathsimple@vodafone.de>>
>     > Reviewed-by: Alex Deucher <alexander.deucher@amd.com
>     <mailto:alexander.deucher@amd.com>>
>
>     I am not sure, but to me this looks like this could fix these kind
>     of gpu
>     lockups that I experience since some time every now and then.
>     The usual symptom is that I get the
>
>     radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
>     GPU lockup (waiting for 0x00682AC3 last fence id 0x00682AC2)
>     [...]
>
>     kernel message. Each time with the fence being off by one like in
>     the example
>     above.
>
>     If this change has the potential to fix this issue I think this
>     particular
>     patch should be considered for the current upstream kernel release.
>
>     Mathias
>
>
> No this patch doesn't. This patch is all about getting proper sync btw 
> different rings.
That's unfortunately true, since we wasn't able to release any code that 
makes direct use of the different rings (yet) it shouldn't really matter 
in practice. I Just wanted to have that fix upstream since it is an 
obvious bug.

Christian.
>
> Sorry for the deception.
>
> Cheers,
> Jerome


[-- Attachment #1.2: Type: text/html, Size: 2978 bytes --]

[-- 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:[~2012-02-23 18:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-23 14:18 [PATCH 1/4] drm/radeon: move ring syncing after bo validation Christian König
2012-02-23 14:18 ` [PATCH 2/4] drm/radeon/kms: no need to align IB like this Christian König
2012-02-23 17:00   ` Jerome Glisse
2012-02-23 18:19     ` Christian König
2012-02-23 14:18 ` [PATCH 3/4] drm/radeon: also make the cs_parse function per ring Christian König
2012-02-24 17:14   ` Jerome Glisse
2012-02-23 14:18 ` [PATCH 4/4] drm/radeon: fix IB debugfs files for multiple cards Christian König
2012-02-23 15:17 ` [PATCH 1/4] drm/radeon: move ring syncing after bo validation Alex Deucher
2012-02-24 17:15   ` Jerome Glisse
2012-02-23 17:05 ` Mathias Fröhlich
2012-02-23 17:32   ` Jerome Glisse
2012-02-23 18:27     ` Christian König [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=4F468516.2010205@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=j.glisse@gmail.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