dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106872] vram sizes reported by the kernel totally off
Date: Mon, 11 Jun 2018 17:15:34 +0000	[thread overview]
Message-ID: <bug-106872-502-L2jOCLEGKz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106872-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1039 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=106872

--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
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 such
BOs can still end up pinned at least partially in CPU visible VRAM, which would
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.

[-- Attachment #1.2: Type: text/html, Size: 1892 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-06-11 17:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09 22:47 [Bug 106872] vram sizes reported by the kernel totally off bugzilla-daemon
2018-06-11 17:15 ` bugzilla-daemon [this message]
2018-06-12  6:59 ` bugzilla-daemon
2018-06-14 15:47 ` 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-106872-502-L2jOCLEGKz@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