From: Fenghua Yu <fenghua.yu@intel.com>
To: "Vinod Koul" <vkoul@kernel.org>, devejiang@kvack.org
Cc: "Fenghua Yu" <fenghua.yu@intel.com>,
Dave Jiang <dave.jiang@intel.com>, Tony Zhu <tony.zhu@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: [PATCH 09/17] mm: export access_remote_vm() symbol
Date: Tue, 3 Jan 2023 08:29:12 -0800 [thread overview]
Message-ID: <20230103162920.1569002-10-fenghua.yu@intel.com> (raw)
In-Reply-To: <20230103162920.1569002-1-fenghua.yu@intel.com>
From: Dave Jiang <dave.jiang@intel.com>
Export access_remote_vm() symbol for driver usage. The idxd driver would
like to use it to write the user's completion record that the hardware
device is not able to write to due to user page fault.
Tested-by: Tony Zhu <tony.zhu@intel.com>
Signed-off-by: Dave Jiang <dave.jiang@intel.com>
Co-developed-by: Fenghua Yu <fenghua.yu@intel.com>
Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
---
mm/memory.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/mm/memory.c b/mm/memory.c
index aad226daf41b..caae4deff987 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -5579,6 +5579,7 @@ int access_remote_vm(struct mm_struct *mm, unsigned long addr,
{
return __access_remote_vm(mm, addr, buf, len, gup_flags);
}
+EXPORT_SYMBOL_GPL(access_remote_vm);
/*
* Access another process' address space.
--
2.32.0
next prev parent reply other threads:[~2023-01-03 16:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230103162920.1569002-1-fenghua.yu@intel.com>
2023-01-03 16:29 ` [PATCH 08/17] iommu: expose iommu_sva_find() to common header Fenghua Yu
2023-01-03 16:29 ` Fenghua Yu [this message]
2023-01-03 16:34 [PATCH 00/17] Enable DSA 2.0 Event Log and completion record faulting features Fenghua Yu
2023-01-03 16:34 ` [PATCH 09/17] mm: export access_remote_vm() symbol Fenghua Yu
2023-01-03 17:45 ` Lorenzo Stoakes
2023-01-03 17:50 ` Lorenzo Stoakes
2023-01-03 19:20 ` Yu, Fenghua
2023-01-03 20:13 ` Lorenzo Stoakes
2023-01-04 5:06 ` Yu, Fenghua
2023-01-04 6:12 ` Alistair Popple
2023-01-04 19:00 ` Yu, Fenghua
2023-01-04 20:00 ` Lorenzo Stoakes
2023-01-04 19:56 ` Lorenzo Stoakes
2023-01-04 21:05 ` Lorenzo Stoakes
2023-01-04 23:57 ` Alistair Popple
2023-01-05 3:08 ` Yu, Fenghua
2023-01-05 3:22 ` Alistair Popple
2023-01-05 20:58 ` Yu, Fenghua
2023-01-05 21:04 ` Lorenzo Stoakes
2023-01-05 7:26 ` Lorenzo Stoakes
2023-01-08 17:36 ` Christoph Hellwig
2023-03-01 23:39 ` Fenghua Yu
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=20230103162920.1569002-10-fenghua.yu@intel.com \
--to=fenghua.yu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.jiang@intel.com \
--cc=devejiang@kvack.org \
--cc=linux-mm@kvack.org \
--cc=tony.zhu@intel.com \
--cc=vkoul@kernel.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.