From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 106872] vram sizes reported by the kernel totally off Date: Mon, 11 Jun 2018 17:15:34 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0770788434==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 147566E368 for ; Mon, 11 Jun 2018 17:15:34 +0000 (UTC) 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 --===============0770788434== Content-Type: multipart/alternative; boundary="15287373330.E7df2daa.32294" Content-Transfer-Encoding: 7bit --15287373330.E7df2daa.32294 Date: Mon, 11 Jun 2018 17:15:33 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D106872 --- Comment #1 from Michel D=C3=A4nzer --- Please attach the dmesg output from the affected system, preferably captured while or after the problem occurs. (In reply to Bas Nieuwenhuizen from comment #0) > e.g. the last report we had kernel reported total VRAM size of > 0xfffffffb3070f000 (16.0 EiB) and a visible VRAM size of 0x86135000 (2.09 > GiB). Not the other way around? One potential issue I can see is that only BOs with AMDGPU_GEM_CREATE_NO_CPU_ACCESS are accounted for invisible_pin_size. But s= uch BOs can still end up pinned at least partially in CPU visible VRAM, which w= ould mess up the calculation of how much visible VRAM currently isn't pinned. One possible solution for this would be for amdgpu_bo_pin_restricted and amdgpu_bo_unpin to walk the list of memory nodes and calculate exactly how = much of each of them lies in visible or invisible VRAM. --=20 You are receiving this mail because: You are the assignee for the bug.= --15287373330.E7df2daa.32294 Date: Mon, 11 Jun 2018 17:15:33 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 1 on bug 10687= 2 from Michel D=C3=A4nzer 
Please attach the dmesg output from the affected system, prefe=
rably captured
while or after the problem occurs.

(In reply to Bas Nieuwenhuizen from comment #0)
> e.g. the last report we had kernel reported tota=
l VRAM size of
> 0xfffffffb3070f000 (16.0 EiB) and a visible VRAM size of 0x86135000 (2=
.09
> GiB).

Not the other way around?

One potential issue I can see is that only BOs with
AMDGPU_GEM_CREATE_NO_CPU_ACCESS are accounted for invisible_pin_size. But s=
uch
BOs can still end up pinned at least partially in CPU visible VRAM, which w=
ould
mess up the calculation of how much visible VRAM currently isn't pinned.

One possible solution for this would be for amdgpu_bo_pin_restricted and
amdgpu_bo_unpin to walk the list of memory nodes and calculate exactly how =
much
of each of them lies in visible or invisible VRAM.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15287373330.E7df2daa.32294-- --===============0770788434== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0770788434==--