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 18:12:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1282499468==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id CFC666E75D for ; Tue, 26 May 2015 11:12:22 -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 --===============1282499468== Content-Type: multipart/alternative; boundary="1432663942.62d2EdF60.5119"; charset="UTF-8" --1432663942.62d2EdF60.5119 Date: Tue, 26 May 2015 18:12:22 +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 #23 from Christian K=C3=B6nig --- (In reply to Michel D=C3=A4nzer from comment #20) > How would it break backwards compatibility? You would need to allow multiple mappings into the same address space per B= O. Which is exactly what I've did for amdgpu, but IIRC that would break the userspace interface because you won't return the mapped address any more wh= en you try to map it multiple times.... > I'm not sure how not tracking > the VA ranges per GEM handle could ever work as expected with several GEM > handles referencing the same BO. Actually it can indeed never work correctly. What we just do all the time is trying to avoid the case that several GEM handles reference the same BO very hard. --=20 You are receiving this mail because: You are the assignee for the bug. --1432663942.62d2EdF60.5119 Date: Tue, 26 May 2015 18:12:22 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Commen= t # 23 on bug 90537<= /a> from Christian K=C3=B6nig 
(In reply to Michel D=C3=A4nzer from comment #20)
> How would it break backwards compatibility?

You would need to allow multiple mappings into the same address space per B=
O.

Which is exactly what I've did for amdgpu, but IIRC that would break the
userspace interface because you won't return the mapped address any more wh=
en
you try to map it multiple times....

> I'm not sure how not tracking
> the VA ranges per GEM handle could ever work as expected with several =
GEM
> handles referencing the same BO.

Actually it can indeed never work correctly. What we just do all the time is
trying to avoid the case that several GEM handles reference the same BO very
hard.

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