All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105633] [amdgpu][bisected] PRIME stuttering tearing
Date: Tue, 20 Mar 2018 20:53:18 +0000	[thread overview]
Message-ID: <bug-105633-502@http.bugs.freedesktop.org/> (raw)


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

https://bugs.freedesktop.org/show_bug.cgi?id=105633

            Bug ID: 105633
           Summary: [amdgpu][bisected] PRIME stuttering tearing
           Product: DRI
           Version: XOrg git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/AMDgpu
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: mike@fireburn.co.uk

I've bisected this to:

commit 9021d2edd259d992cf8b5b48791ab50829129de7                                 
Author: Christian König <christian.koenig@amd.com>                              
Date:   Mon Feb 19 11:29:35 2018 +0100                                          

    drm/amdgpu: mitigate workaround for i915                                    

    To be able to use DRI_PRIME with amdgpu and i915 we add all our fences      
    only as exclusive ones.                                                     

    Disable that behavior when sharing between amdgpu itself cause it           
    hinders concurrent execution.                                               

    Signed-off-by: Christian König <christian.koenig@amd.com>                   
    Reviewed-by: Alex Deucher <alexander.deucher@amd.com>                       
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>   

If I revert that and a bit of:

commit 59dd47728625e6f8e77f888d00596c9fb7057540
Author: Christian König <christian.koenig@amd.com>
Date:   Tue Feb 20 19:51:02 2018 +0100

    drm/amdgpu: further mitigate workaround for i915

    Disable the workaround on imported BOs as well.

    Signed-off-by: Christian König <christian.koenig@amd.com>
    Reviewed-by: Alex Deucher <alexdeucher@amd.com>                             
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>   

To work around the compilation issue, things go back to normal

-- 
You are receiving this mail because:
You are the assignee for the bug.

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

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

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

             reply	other threads:[~2018-03-20 20:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 20:53 bugzilla-daemon [this message]
2018-03-21 13:00 ` [Bug 105633] [amdgpu][bisected] PRIME stuttering tearing bugzilla-daemon

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=bug-105633-502@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --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 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.