From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 97594] [amdgpu SI] "drm/amd/amdgpu: Add GRBM lock to various SI functions" breaks amdgpu support for SI
Date: Wed, 07 Sep 2016 12:05:18 +0000 [thread overview]
Message-ID: <bug-97594-502-Lz8ZPCuwBS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-97594-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 470 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=97594
--- Comment #7 from Tom St Denis <tom.stdenis@amd.com> ---
The problem is a double lock. The grbm_idx_mutex lock is taken in
gfx_v6_0_get_cu_info() which then calls gfx_v6_0_get_cu_active_bitmap() which
also takes the lock.
The fix is to remove the lock and the select from the parent function. I'll
attach a patch momentarily.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1365 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
next prev parent reply other threads:[~2016-09-07 12:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 21:31 [Bug 97594] [amdgpu SI] "drm/amd/amdgpu: Add GRBM lock to various SI functions" breaks amdgpu support for SI bugzilla-daemon
2016-09-04 21:45 ` bugzilla-daemon
2016-09-04 21:53 ` bugzilla-daemon
2016-09-06 18:59 ` bugzilla-daemon
2016-09-06 22:03 ` bugzilla-daemon
2016-09-07 3:45 ` bugzilla-daemon
2016-09-07 12:05 ` bugzilla-daemon
2016-09-07 12:05 ` bugzilla-daemon [this message]
2016-09-07 12:06 ` bugzilla-daemon
2016-09-07 18:46 ` bugzilla-daemon
2016-09-08 7:15 ` 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-97594-502-Lz8ZPCuwBS@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 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).