From: "Yang, Philip" <Philip.Yang-5C7GfCeVMHo@public.gmane.org>
To: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Cc: "Yang, Philip" <Philip.Yang-5C7GfCeVMHo@public.gmane.org>
Subject: [PATCH] drm/amdgpu: select ARCH_HAS_HMM and ZONE_DEVICE option
Date: Wed, 20 Feb 2019 18:56:15 +0000 [thread overview]
Message-ID: <20190220185544.19602-1-Philip.Yang@amd.com> (raw)
Those options are needed to support HMM
Change-Id: Ieb7bb3bcec07245d79a02793e6728228decc400a
Signed-off-by: Philip Yang <Philip.Yang@amd.com>
---
drivers/gpu/drm/amd/amdgpu/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/gpu/drm/amd/amdgpu/Kconfig b/drivers/gpu/drm/amd/amdgpu/Kconfig
index 960a63355705..63f0542bc34b 100644
--- a/drivers/gpu/drm/amd/amdgpu/Kconfig
+++ b/drivers/gpu/drm/amd/amdgpu/Kconfig
@@ -26,7 +26,9 @@ config DRM_AMDGPU_CIK
config DRM_AMDGPU_USERPTR
bool "Always enable userptr write support"
depends on DRM_AMDGPU
+ select ARCH_HAS_HMM
select HMM_MIRROR
+ select ZONE_DEVICE
help
This option selects CONFIG_HMM and CONFIG_HMM_MIRROR if it
isn't already selected to enabled full userptr support.
--
2.17.1
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
next reply other threads:[~2019-02-20 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 18:56 Yang, Philip [this message]
[not found] ` <20190220185544.19602-1-Philip.Yang-5C7GfCeVMHo@public.gmane.org>
2019-02-20 19:18 ` [PATCH] drm/amdgpu: select ARCH_HAS_HMM and ZONE_DEVICE option Kuehling, Felix
[not found] ` <1dfb54a4-67bf-2e96-40f4-7bfe24284232-5C7GfCeVMHo@public.gmane.org>
2019-02-20 22:12 ` Jerome Glisse
[not found] ` <20190220221243.GA29398-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2019-02-20 22:39 ` Kuehling, Felix
[not found] ` <d52f74c1-a9c2-d265-993d-dae3d367bf70-5C7GfCeVMHo@public.gmane.org>
2019-02-20 23:34 ` Jerome Glisse
[not found] ` <20190220233456.GB11325-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2019-02-21 0:17 ` Kuehling, Felix
[not found] ` <3b6bcf86-c871-b23d-1da8-fe5b4d4ea081-5C7GfCeVMHo@public.gmane.org>
2019-02-21 0:25 ` Jerome Glisse
[not found] ` <20190221002542.GB24489-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2019-02-21 17:36 ` Yang, Philip
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=20190220185544.19602-1-Philip.Yang@amd.com \
--to=philip.yang-5c7gfcevmho@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.