linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Izik Eidus <ieidus@redhat.com>
To: akpm@linux-foundation.org
Cc: hugh.dickins@tiscali.co.uk, aarcange@redhat.com,
	chrisw@redhat.com, avi@redhat.com, riel@redhat.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	nickpiggin@yahoo.com.au, ieidus@redhat.com
Subject: [PATCH 01/10] ksm: add mmu_notifier set_pte_at_notify()
Date: Fri, 17 Jul 2009 20:30:41 +0300	[thread overview]
Message-ID: <1247851850-4298-2-git-send-email-ieidus@redhat.com> (raw)
In-Reply-To: <1247851850-4298-1-git-send-email-ieidus@redhat.com>

From: Izik Eidus <ieidus@redhat.com>

The set_pte_at_notify() macro allows setting a pte in the shadow page
table directly, instead of flushing the shadow page table entry and then
getting vmexit to set it.  It uses a new change_pte() callback to do so.

set_pte_at_notify() is an optimization for kvm, and other users of
mmu_notifiers, for COW pages.  It is useful for kvm when ksm is used,
because it allows kvm not to have to receive vmexit and only then map
the ksm page into the shadow page table, but instead map it directly
at the same time as Linux maps the page into the host page table.

Users of mmu_notifiers who don't implement new mmu_notifier_change_pte()
callback will just receive the mmu_notifier_invalidate_page() callback.

Signed-off-by: Izik Eidus <ieidus@redhat.com>
Signed-off-by: Chris Wright <chrisw@redhat.com>
Signed-off-by: Hugh Dickins <hugh.dickins@tiscali.co.uk>
---
 include/linux/mmu_notifier.h |   34 ++++++++++++++++++++++++++++++++++
 mm/memory.c                  |    9 +++++++--
 mm/mmu_notifier.c            |   20 ++++++++++++++++++++
 3 files changed, 61 insertions(+), 2 deletions(-)

diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
index b77486d..4e02ee2 100644
--- a/include/linux/mmu_notifier.h
+++ b/include/linux/mmu_notifier.h
@@ -62,6 +62,15 @@ struct mmu_notifier_ops {
 				 unsigned long address);
 
 	/*
+	 * change_pte is called in cases that pte mapping to page is changed:
+	 * for example, when ksm remaps pte to point to a new shared page.
+	 */
+	void (*change_pte)(struct mmu_notifier *mn,
+			   struct mm_struct *mm,
+			   unsigned long address,
+			   pte_t pte);
+
+	/*
 	 * Before this is invoked any secondary MMU is still ok to
 	 * read/write to the page previously pointed to by the Linux
 	 * pte because the page hasn't been freed yet and it won't be
@@ -154,6 +163,8 @@ extern void __mmu_notifier_mm_destroy(struct mm_struct *mm);
 extern void __mmu_notifier_release(struct mm_struct *mm);
 extern int __mmu_notifier_clear_flush_young(struct mm_struct *mm,
 					  unsigned long address);
+extern void __mmu_notifier_change_pte(struct mm_struct *mm,
+				      unsigned long address, pte_t pte);
 extern void __mmu_notifier_invalidate_page(struct mm_struct *mm,
 					  unsigned long address);
 extern void __mmu_notifier_invalidate_range_start(struct mm_struct *mm,
@@ -175,6 +186,13 @@ static inline int mmu_notifier_clear_flush_young(struct mm_struct *mm,
 	return 0;
 }
 
+static inline void mmu_notifier_change_pte(struct mm_struct *mm,
+					   unsigned long address, pte_t pte)
+{
+	if (mm_has_notifiers(mm))
+		__mmu_notifier_change_pte(mm, address, pte);
+}
+
 static inline void mmu_notifier_invalidate_page(struct mm_struct *mm,
 					  unsigned long address)
 {
@@ -236,6 +254,16 @@ static inline void mmu_notifier_mm_destroy(struct mm_struct *mm)
 	__young;							\
 })
 
+#define set_pte_at_notify(__mm, __address, __ptep, __pte)		\
+({									\
+	struct mm_struct *___mm = __mm;					\
+	unsigned long ___address = __address;				\
+	pte_t ___pte = __pte;						\
+									\
+	set_pte_at(___mm, ___address, __ptep, ___pte);			\
+	mmu_notifier_change_pte(___mm, ___address, ___pte);		\
+})
+
 #else /* CONFIG_MMU_NOTIFIER */
 
 static inline void mmu_notifier_release(struct mm_struct *mm)
@@ -248,6 +276,11 @@ static inline int mmu_notifier_clear_flush_young(struct mm_struct *mm,
 	return 0;
 }
 
+static inline void mmu_notifier_change_pte(struct mm_struct *mm,
+					   unsigned long address, pte_t pte)
+{
+}
+
 static inline void mmu_notifier_invalidate_page(struct mm_struct *mm,
 					  unsigned long address)
 {
@@ -273,6 +306,7 @@ static inline void mmu_notifier_mm_destroy(struct mm_struct *mm)
 
 #define ptep_clear_flush_young_notify ptep_clear_flush_young
 #define ptep_clear_flush_notify ptep_clear_flush
+#define set_pte_at_notify set_pte_at
 
 #endif /* CONFIG_MMU_NOTIFIER */
 
diff --git a/mm/memory.c b/mm/memory.c
index 6521619..8159a62 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -2113,9 +2113,14 @@ gotten:
 		 * seen in the presence of one thread doing SMC and another
 		 * thread doing COW.
 		 */
-		ptep_clear_flush_notify(vma, address, page_table);
+		ptep_clear_flush(vma, address, page_table);
 		page_add_new_anon_rmap(new_page, vma, address);
-		set_pte_at(mm, address, page_table, entry);
+		/*
+		 * We call the notify macro here because, when using secondary
+		 * mmu page tables (such as kvm shadow page tables), we want the
+		 * new page to be mapped directly into the secondary page table.
+		 */
+		set_pte_at_notify(mm, address, page_table, entry);
 		update_mmu_cache(vma, address, entry);
 		if (old_page) {
 			/*
diff --git a/mm/mmu_notifier.c b/mm/mmu_notifier.c
index 5f4ef02..7e33f2c 100644
--- a/mm/mmu_notifier.c
+++ b/mm/mmu_notifier.c
@@ -99,6 +99,26 @@ int __mmu_notifier_clear_flush_young(struct mm_struct *mm,
 	return young;
 }
 
+void __mmu_notifier_change_pte(struct mm_struct *mm, unsigned long address,
+			       pte_t pte)
+{
+	struct mmu_notifier *mn;
+	struct hlist_node *n;
+
+	rcu_read_lock();
+	hlist_for_each_entry_rcu(mn, n, &mm->mmu_notifier_mm->list, hlist) {
+		if (mn->ops->change_pte)
+			mn->ops->change_pte(mn, mm, address, pte);
+		/*
+		 * Some drivers don't have change_pte,
+		 * so we must call invalidate_page in that case.
+		 */
+		else if (mn->ops->invalidate_page)
+			mn->ops->invalidate_page(mn, mm, address);
+	}
+	rcu_read_unlock();
+}
+
 void __mmu_notifier_invalidate_page(struct mm_struct *mm,
 					  unsigned long address)
 {
-- 
1.5.6.5

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-07-17 17:27 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 17:30 [PATCH 00/10] ksm resend Izik Eidus
2009-07-17 17:30 ` Izik Eidus [this message]
2009-07-17 17:30   ` [PATCH 02/10] ksm: first tidy up madvise_vma() Izik Eidus
2009-07-17 17:30     ` [PATCH 03/10] ksm: define MADV_MERGEABLE and MADV_UNMERGEABLE Izik Eidus
2009-07-17 17:30       ` [PATCH 04/10] ksm: the mm interface to ksm Izik Eidus
2009-07-17 17:30         ` [PATCH 05/10] ksm: no debug in page_dup_rmap() Izik Eidus
2009-07-17 17:30           ` [PATCH 06/10] ksm: identify PageKsm pages Izik Eidus
2009-07-17 17:30             ` [PATCH 07/10] ksm: Kernel SamePage Merging Izik Eidus
2009-07-17 17:30               ` [PATCH 08/10] ksm: prevent mremap move poisoning Izik Eidus
2009-07-17 17:30                 ` [PATCH 09/10] ksm: change copyright message Izik Eidus
2009-07-17 17:30                   ` [PATCH 10/10] ksm: change ksm nice level to be 5 Izik Eidus
2009-07-19 13:50                     ` Hugh Dickins
2009-07-20  4:50                     ` Balbir Singh
2009-07-20 11:48                       ` Izik Eidus
2009-07-20 12:14                         ` Balbir Singh
2009-07-20 18:38                     ` Rik van Riel
2009-07-19 13:49                   ` [PATCH 09/10] ksm: change copyright message Hugh Dickins
2009-07-20 18:37                   ` Rik van Riel
2009-07-20 18:37                 ` [PATCH 08/10] ksm: prevent mremap move poisoning Rik van Riel
2009-07-20 18:35               ` [PATCH 07/10] ksm: Kernel SamePage Merging Rik van Riel
2009-07-18  2:45             ` [PATCH 06/10] ksm: identify PageKsm pages Wu Fengguang
2009-07-20 18:32             ` Rik van Riel
2009-07-21 17:51             ` Andrea Arcangeli
2009-07-21 17:55               ` Rik van Riel
2009-07-21 18:01                 ` Andrea Arcangeli
2009-07-21 18:17                   ` Izik Eidus
2009-07-22 12:54                 ` Hugh Dickins
2009-07-23  2:06                   ` KAMEZAWA Hiroyuki
2009-07-23 11:43                     ` Hugh Dickins
2009-07-23 11:49                     ` Lee Schermerhorn
2009-07-22 12:45               ` Hugh Dickins
2009-07-22 16:52                 ` Andrea Arcangeli
2009-07-23 11:36                   ` Hugh Dickins
2009-07-20 18:11           ` [PATCH 05/10] ksm: no debug in page_dup_rmap() Rik van Riel
2009-07-21  7:16             ` Nick Piggin
2009-07-20 17:38         ` [PATCH 04/10] ksm: the mm interface to ksm Rik van Riel
2009-07-20 15:09       ` [PATCH 03/10] ksm: define MADV_MERGEABLE and MADV_UNMERGEABLE Rik van Riel
2009-07-20 15:44       ` Ralf Baechle
2009-07-20 15:05     ` [PATCH 02/10] ksm: first tidy up madvise_vma() Rik van Riel
2009-07-20 14:48   ` [PATCH 01/10] ksm: add mmu_notifier set_pte_at_notify() Rik van Riel
2009-07-21 17:59 ` [PATCH 00/10] ksm resend Andrea Arcangeli
2009-07-22 13:05   ` Hugh Dickins

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=1247851850-4298-2-git-send-email-ieidus@redhat.com \
    --to=ieidus@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=avi@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=hugh.dickins@tiscali.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).