From: Shane Francis <bigbeeshane@gmail.com>
To: dri-devel@lists.freedesktop.org
Cc: bigbeeshane@gmail.com
Subject: [PATCH 0/2] AMDGPU / DRM Fix mapping of user pages
Date: Mon, 23 Mar 2020 20:51:35 +0000 [thread overview]
Message-ID: <20200323205137.136530-1-bigbeeshane@gmail.com> (raw)
This patch set is to fix a bug in amdgpu that results in
a crash when dma_map_sg combines segments. There are 2
shortfalls in the current kernel.
1) AMDGPU assumes that the requested and created segments
from dma_map_sg are equal
2) drm_prime does not allow for setting the segment length
via the correct dma macro
Shane Francis (2):
drm/prime: correct logic for mapping sg to arrays
drm/amdgpu: fix scatter-gather mapping with user pages
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 7 +--
drivers/gpu/drm/drm_prime.c | 71 +++++++++++++++++++++----
include/drm/drm_prime.h | 5 ++
3 files changed, 71 insertions(+), 12 deletions(-)
--
2.26.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2020-03-23 20:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 20:51 Shane Francis [this message]
2020-03-23 20:51 ` [PATCH 1/2] drm/prime: correct logic for mapping sg to arrays Shane Francis
2020-03-23 20:51 ` [PATCH 2/2] drm/amdgpu: fix scatter-gather mapping with user pages Shane Francis
2020-03-23 21:36 ` Alex Deucher
2020-03-23 22:38 ` Shane Francis
2020-03-23 23:51 ` [PATCH v2 0/3] AMDGPU / RADEON / DRM Fix mapping of " Shane Francis
2020-03-23 23:51 ` [PATCH v2 1/3] drm/prime: correct logic for mapping sg to arrays Shane Francis
2020-03-23 23:51 ` [PATCH v2 2/3] drm/amdgpu: fix scatter-gather mapping with user pages Shane Francis
2020-03-23 23:51 ` [PATCH v2 3/3] drm/radeon: " Shane Francis
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=20200323205137.136530-1-bigbeeshane@gmail.com \
--to=bigbeeshane@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).