From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90537] radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL)
Date: Thu, 21 May 2015 20:09:39 +0000 [thread overview]
Message-ID: <bug-90537-502-xonWATKRpq@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-90537-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1515 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=90537
--- Comment #5 from pstglia@gmail.com ---
Hi Christian,
> Watch out for memory leaks as well.
>
> When mesa drops the last reference to the BO by closing it's handle the VA
> mapping should go away automatically. That's the reason why it works for X
> and EGL.
>
> What you see here is that you manually need to remove the VA mapping because
> there is still a reference to the BO outside of mesa.
>
> Could be intentional, but could be a bug as well.
Thanks for pointing this out. Just a question: In this case (bug on application
on mapping BOs/VAs) shouldn't we have a crash using other drivers? With r600g
we don't have this problem (tested with an ARUBA A10 5800K), just on radeonsi
(at least on the tests I performed, which are basically running "Antutu
Benchmark" and some other apps).
However r600g/other drivers/hardwares can handle this in a different manner of
course, which could explain why we don't experience this on other hardwares.
>
> Anyway Michels patch is clearly a good idea.
I've uploaded an testing Android-x86 ISO with Michel patch applied. It's using
Lollipop (5.1), Mesa 10.5.4, Kernel 4.0.3 and LLVM 3.5svn (AOSP). It's also
enabled for radeonsi (this is the main purpose). In case anyone wants to test
it on a radeonsi hardware, here's the link:
https://drive.google.com/file/d/0Bx12U5yGNcQCRWdoWWtNdC0weW8/view?usp=sharing
Thank you all!
pstglia
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2538 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-05-21 20:09 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 14:06 [Bug 90537] radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL) bugzilla-daemon
2015-05-20 14:26 ` bugzilla-daemon
2015-05-20 14:28 ` bugzilla-daemon
2015-05-21 2:12 ` bugzilla-daemon
2015-05-21 19:14 ` bugzilla-daemon
2015-05-21 19:19 ` bugzilla-daemon
2015-05-21 20:09 ` bugzilla-daemon [this message]
2015-05-22 8:53 ` bugzilla-daemon
2015-05-22 9:30 ` bugzilla-daemon
2015-05-22 11:49 ` bugzilla-daemon
2015-05-22 12:07 ` bugzilla-daemon
2015-05-22 12:16 ` bugzilla-daemon
2015-05-23 1:22 ` bugzilla-daemon
2015-05-24 14:25 ` bugzilla-daemon
2015-05-24 14:26 ` bugzilla-daemon
2015-05-24 14:29 ` bugzilla-daemon
2015-05-25 12:10 ` bugzilla-daemon
2015-05-25 16:32 ` bugzilla-daemon
2015-05-26 8:12 ` bugzilla-daemon
2015-05-26 9:06 ` bugzilla-daemon
2015-05-26 9:06 ` bugzilla-daemon
2015-05-26 9:30 ` bugzilla-daemon
2015-05-26 16:16 ` bugzilla-daemon
2015-05-26 18:09 ` bugzilla-daemon
2015-05-26 18:12 ` bugzilla-daemon
2015-05-27 10:00 ` bugzilla-daemon
2015-06-25 2:46 ` 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-90537-502-xonWATKRpq@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).