From: "Kuehling, Felix" <Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
To: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Cc: "Zeng, Oak" <Oak.Zeng-5C7GfCeVMHo@public.gmane.org>,
"Koenig,
Christian" <Christian.Koenig-5C7GfCeVMHo@public.gmane.org>
Subject: [PATCH 0/4] KFD: Mapping-specific MTYPEs on Arcturus
Date: Fri, 23 Aug 2019 21:33:45 +0000 [thread overview]
Message-ID: <20190823213249.10749-1-Felix.Kuehling@amd.com> (raw)
This is a simplified version of Oak's patch series, addressing some of
the concerns raised during code review. Patches 1-3 are taken directly
from Oak's series. Patch 4 is a simplified version of Oak's patches
3 and 5 that keeps all the KFD memory type abstractions out of the GMC
IP-version-specific code.
Compile tested only.
Felix Kuehling (1):
drm/amdgpu: Determing PTE flags separately for each mapping
Oak Zeng (3):
drm/amdgpu: Extends amdgpu vm definitions
drm/amdgpu: Support new arcturus mtype
drm/amdgpu: Support snooped PTE flag
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.h | 2 +-
.../gpu/drm/amd/amdgpu/amdgpu_amdkfd_gpuvm.c | 60 ++++++++++++++-----
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 9 ++-
drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 6 ++
drivers/gpu/drm/amd/include/vega10_enum.h | 1 +
include/uapi/drm/amdgpu_drm.h | 4 ++
6 files changed, 63 insertions(+), 19 deletions(-)
--
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-08-23 21:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 21:33 Kuehling, Felix [this message]
[not found] ` <20190823213249.10749-1-Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
2019-08-23 21:33 ` [PATCH 2/4] drm/amdgpu: Support new arcturus mtype Kuehling, Felix
2019-08-23 21:33 ` [PATCH 1/4] drm/amdgpu: Extends amdgpu vm definitions Kuehling, Felix
[not found] ` <20190823213249.10749-2-Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
2019-08-24 11:12 ` Christian König
2019-08-23 21:33 ` [PATCH 3/4] drm/amdgpu: Support snooped PTE flag Kuehling, Felix
[not found] ` <20190823213249.10749-4-Felix.Kuehling-5C7GfCeVMHo@public.gmane.org>
2019-08-24 11:13 ` Christian König
[not found] ` <f09e6893-347b-4ade-76e5-ad37d8e4e782-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-08-24 16:24 ` Kuehling, Felix
[not found] ` <a7f9ad48-2e46-5415-e2a8-1738a101d716-5C7GfCeVMHo@public.gmane.org>
2019-08-24 18:59 ` Christian König
[not found] ` <96b6ac1d-de87-3fdb-a531-af4b0a42f1d5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2019-08-26 15:45 ` Kuehling, Felix
[not found] ` <4b48fc1a-6ee2-bb60-0518-ea9c6346b8d6-5C7GfCeVMHo@public.gmane.org>
2019-08-26 17:16 ` Koenig, Christian
[not found] ` <89bf5baa-4b63-e40a-7995-fa35bad988b7-5C7GfCeVMHo@public.gmane.org>
2019-08-26 18:03 ` Kuehling, Felix
[not found] ` <216f63db-78c5-1098-bea5-2f379b0bf051-5C7GfCeVMHo@public.gmane.org>
2019-08-26 18:12 ` Koenig, Christian
[not found] ` <49ba47da-a225-5a21-9014-ccc316c55b60-5C7GfCeVMHo@public.gmane.org>
2019-08-26 22:32 ` Kuehling, Felix
2019-08-23 21:33 ` [PATCH 4/4] drm/amdgpu: Determing PTE flags separately for each mapping Kuehling, Felix
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=20190823213249.10749-1-Felix.Kuehling@amd.com \
--to=felix.kuehling-5c7gfcevmho@public.gmane.org \
--cc=Christian.Koenig-5C7GfCeVMHo@public.gmane.org \
--cc=Oak.Zeng-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.