From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93460] [amdgpu] Ooops during shutdown - amdgpu_vm_grab_id
Date: Mon, 21 Dec 2015 14:57:32 +0000 [thread overview]
Message-ID: <bug-93460-502-rncleMkf6f@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93460-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 631 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=93460
--- Comment #7 from Christian König <deathsimple@vodafone.de> ---
(In reply to david1.zhou@amd.com from comment #6)
> Maybe we shall avoid to use fence for vmid, instead using LRU list.
Yeah, thought about that as well. The problem is that we used to have an LRU
list and I switched to fences because they had less overhead.
We still need to keep the fences around for synchronization, so I'm not sure if
that would really help.
The real price question is what is going wrong here?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1545 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
next prev parent reply other threads:[~2015-12-21 14:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-20 14:54 [Bug 93460] [amdgpu] Ooops during shutdown - amdgpu_vm_grab_id bugzilla-daemon
2015-12-20 15:09 ` bugzilla-daemon
2015-12-20 15:35 ` bugzilla-daemon
2015-12-21 4:08 ` bugzilla-daemon
2015-12-21 7:21 ` bugzilla-daemon
2015-12-21 8:55 ` bugzilla-daemon
2015-12-21 9:23 ` bugzilla-daemon
2015-12-21 14:57 ` bugzilla-daemon [this message]
2015-12-22 2:49 ` bugzilla-daemon
2016-04-15 17:50 ` 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-93460-502-rncleMkf6f@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