All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107898] "kfd: Failed to resume IOMMU for device 1002:15dd" on Raven Ridge
Date: Mon, 01 Oct 2018 18:40:10 +0000	[thread overview]
Message-ID: <bug-107898-502-c4xBi1jmV7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107898-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from Felix Kuehling <felix.kuehling@amd.com> ---
rocminfo reports both the CPU and the GPU.

If OpenCL can't use the CPU as a compute device, that's probably a limitation
of the OpenCL implementation.

The max memory allocation size is strange. rocminfo reports a single 16GB
memory pool attached to the CPU. That's system memory from the CRAT table and
looks reasonable. It should be possible to use at least 3/8 of that with the
upstream KFD. If CLinfo is reporting something different I'm wondering if it's
an OpenCL limitation rather than a ROCm limitation.

If you're interested in the raw information reported by KFD to user mode,
checkout /sys/class/kfd/kfd/topology/nodes. On an APU there should be only one
node (0). Underneath that you'll find node properties as well as memory
properties that may be interesting.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1830 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

  parent reply	other threads:[~2018-10-01 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  7:33 [Bug 107898] "kfd: Failed to resume IOMMU for device 1002:15dd" on Raven Ridge bugzilla-daemon
2018-09-11  8:49 ` bugzilla-daemon
2018-09-11  8:53 ` bugzilla-daemon
2018-09-11 20:48 ` bugzilla-daemon
2018-09-12  5:19 ` bugzilla-daemon
2018-09-12  5:21 ` bugzilla-daemon
2018-09-12 10:16 ` bugzilla-daemon
2018-09-12 10:17 ` bugzilla-daemon
2018-09-13 20:05 ` bugzilla-daemon
2018-09-14  7:40 ` bugzilla-daemon
2018-09-20  9:00 ` bugzilla-daemon
2018-09-20  9:01 ` bugzilla-daemon
2018-10-01 18:40 ` bugzilla-daemon [this message]
2018-10-10 12:07 ` bugzilla-daemon
2018-11-14 10:44 ` bugzilla-daemon
2019-11-19  7:53 ` 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-107898-502-c4xBi1jmV7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.