From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 90537] radeonsi bo/va conflict on RADEON_GEM_VA (rscreen->ws->buffer_from_handle returns NULL) Date: Tue, 26 May 2015 09:06:17 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1502727000==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 9793A6E233 for ; Tue, 26 May 2015 02:06:17 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1502727000== Content-Type: multipart/alternative; boundary="1432631177.5bdf0.16233"; charset="UTF-8" --1432631177.5bdf0.16233 Date: Tue, 26 May 2015 09:06:17 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable https://bugs.freedesktop.org/show_bug.cgi?id=3D90537 --- Comment #18 from Christian K=C3=B6nig --- (In reply to Michel D=C3=A4nzer from comment #17) > My feeling is that the only proper solution might be to track the VA rang= es > per GEM handle instead of per BO in the kernel. Christian, would that be > feasible in the radeon driver? I'm working on that problem for years now, tracking VA ranges per GEM handle isn't really doable either (e.g. without breaking backward compatibility). Haven't come up with a good solution so far. > BTW, I think the dmesg output would be more useful without all the debugg= ing > output enabled. That makes it like looking for a needle in a haystack. Yeah, agree. That is a bit two much. --=20 You are receiving this mail because: You are the assignee for the bug. --1432631177.5bdf0.16233 Date: Tue, 26 May 2015 09:06:17 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 18 on bug 90537<= /a> from Christian K=C3=B6nig 
(In reply to Michel D=C3=A4nzer from comment #17)
> My feeling is that the only proper solution migh=
t be to track the VA ranges
> per GEM handle instead of per BO in the kernel. Christian, would that =
be
> feasible in the radeon driver?

I'm working on that problem for years now, tracking VA ranges per GEM handle
isn't really doable either (e.g. without breaking backward compatibility).
Haven't come up with a good solution so far.

> BTW, I think the dmesg output would be more usef=
ul without all the debugging
> output enabled. That makes it like looking for a needle in a haystack.=


Yeah, agree. That is a bit two much.

You are receiving this mail because: =20=20=20=20=20=20
  • You are the assignee for the bug.
--1432631177.5bdf0.16233-- --===============1502727000== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1502727000==--