From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: linux-kernel@vger.kernel.org
Cc: jroedel@suse.de
Subject: [PATCH 1/2] mm: export find_extend_vma and handle_mm_fault for driver use
Date: Fri, 24 Oct 2014 12:34:30 -0700 [thread overview]
Message-ID: <1414179271-7621-1-git-send-email-jbarnes@virtuousgeek.org> (raw)
This lets drivers like the AMD IOMMUv2 driver handle faults a bit more
simply, rather than doing tricks with page refs and get_user_pages().
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
---
mm/memory.c | 1 +
mm/mmap.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/mm/memory.c b/mm/memory.c
index 1cc6bfb..969ff0c 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -3378,6 +3378,7 @@ int handle_mm_fault(struct mm_struct *mm, struct vm_area_struct *vma,
return ret;
}
+EXPORT_SYMBOL_GPL(handle_mm_fault);
#ifndef __PAGETABLE_PUD_FOLDED
/*
diff --git a/mm/mmap.c b/mm/mmap.c
index 7f85520..2ee7971 100644
--- a/mm/mmap.c
+++ b/mm/mmap.c
@@ -2359,6 +2359,8 @@ find_extend_vma(struct mm_struct *mm, unsigned long addr)
}
#endif
+EXPORT_SYMBOL_GPL(find_extend_vma);
+
/*
* Ok - we have the memory areas we should free on the vma list,
* so release them, and do the vma updates.
--
1.9.1
next reply other threads:[~2014-10-24 19:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 19:34 Jesse Barnes [this message]
2014-10-24 19:34 ` [PATCH 2/2] iommu/amd: use handle_mm_fault directly Jesse Barnes
2014-10-27 15:13 ` [PATCH 1/2] mm: export find_extend_vma and handle_mm_fault for driver use Joerg Roedel
2014-10-27 15:15 ` Oded Gabbay
2014-10-27 15:35 ` Jesse Barnes
2014-10-27 15:37 ` Oded Gabbay
2014-10-29 9:33 ` Oded Gabbay
2014-10-29 14:37 ` Jesse Barnes
2014-11-05 12:03 ` Joerg Roedel
2014-11-05 21:51 ` Jesse Barnes
2014-11-06 8:51 ` Oded Gabbay
2014-11-06 13:03 ` Joerg Roedel
2014-11-06 13:01 ` Joerg Roedel
2014-11-12 22:07 ` Jesse Barnes
2014-11-17 16:53 ` Joerg Roedel
2014-11-12 22:10 Jesse Barnes
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=1414179271-7621-1-git-send-email-jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.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 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®