From: Felix Kuehling <felix.kuehling@amd.com>
To: <linux-kernel@vger.kernel.org>
Cc: Takashi Iwai <tiwai@suse.com>,
Harish Kasiviswanathan <harish.kasiviswanathan@amd.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] kernel: Export mm_access
Date: Tue, 23 May 2017 16:17:29 -0400 [thread overview]
Message-ID: <5a9607b4-d2ac-fc7b-e43b-1e73c2651071@amd.com> (raw)
From: Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>
Exporting mm_access, which is required for implementing accelerated
equivalents of process_vm_readv/process_vm_writev for GPU memory in KFD
(AMD's GPU compute driver). This allows us to apply all the same remote
process memory access policies.
Signed-off-by: Harish Kasiviswanathan <Harish.Kasiviswanathan@amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
---
Current KFD with AMD discrete GPU support is not yet upstream, but we
are working on getting it upstream for 4.13 or 4.14 depending on how we
line up with Dave Airlie's merge windows.
For reference, recent releases of ROCm (AMD's Radeon Open Compute
Platform software stack) with fully open-source user mode and kernel
code can be found on GitHub:
https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/tree/roc-1.5.0
kernel/fork.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/fork.c b/kernel/fork.c
index aa1076c..0849896 100644
--- a/kernel/fork.c
+++ b/kernel/fork.c
@@ -1060,6 +1060,7 @@ struct mm_struct *mm_access(struct task_struct
*task, unsigned int mode)
return mm;
}
+EXPORT_SYMBOL_GPL(mm_access);
static void complete_vfork_done(struct task_struct *tsk)
{
next reply other threads:[~2017-05-23 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 20:17 Felix Kuehling [this message]
2017-05-23 21:14 ` Andrew Morton
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=5a9607b4-d2ac-fc7b-e43b-1e73c2651071@amd.com \
--to=felix.kuehling@amd.com \
--cc=akpm@linux-foundation.org \
--cc=harish.kasiviswanathan@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.com \
/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
all inboxes | Powered by JetHome®