All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, jglisse@google.com, mhocko@suse.com,
	vbabka@suse.cz, hannes@cmpxchg.org, mgorman@suse.de,
	dave@stgolabs.net, willy@infradead.org, liam.howlett@oracle.com,
	peterz@infradead.org, ldufour@linux.ibm.com,
	laurent.dufour@fr.ibm.com, paulmck@kernel.org, luto@kernel.org,
	songliubraving@fb.com, peterx@redhat.com, david@redhat.com,
	dhowells@redhat.com, hughd@google.com, bigeasy@linutronix.de,
	kent.overstreet@linux.dev, rientjes@google.com,
	axelrasmussen@google.com, joelaf@google.com, minchan@google.com,
	surenb@google.com, kernel-team@android.com, linux-mm@kvack.org,
	linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org, x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: [RFC PATCH RESEND 22/28] x86/mm: try VMA lock-based page fault handling first
Date: Thu,  1 Sep 2022 10:35:10 -0700	[thread overview]
Message-ID: <20220901173516.702122-23-surenb@google.com> (raw)
In-Reply-To: <20220901173516.702122-1-surenb@google.com>

Attempt VMA lock-based page fault handling first, and fall back to the
existing mmap_lock-based handling if that fails.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 arch/x86/mm/fault.c | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index fa71a5d12e87..35e74e3dc2c1 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -19,6 +19,7 @@
 #include <linux/uaccess.h>		/* faulthandler_disabled()	*/
 #include <linux/efi.h>			/* efi_crash_gracefully_on_page_fault()*/
 #include <linux/mm_types.h>
+#include <linux/mm.h>			/* find_and_lock_vma() */
 
 #include <asm/cpufeature.h>		/* boot_cpu_has, ...		*/
 #include <asm/traps.h>			/* dotraplinkage, ...		*/
@@ -1323,6 +1324,38 @@ void do_user_addr_fault(struct pt_regs *regs,
 	}
 #endif
 
+#ifdef CONFIG_PER_VMA_LOCK
+	if (!(flags & FAULT_FLAG_USER) || atomic_read(&mm->mm_users) == 1)
+		goto lock_mmap;
+
+	vma = find_and_lock_anon_vma(mm, address);
+	if (!vma)
+		goto lock_mmap;
+
+	if (unlikely(access_error(error_code, vma))) {
+		vma_read_unlock(vma);
+		goto lock_mmap;
+	}
+	fault = handle_mm_fault(vma, address, flags | FAULT_FLAG_VMA_LOCK, regs);
+	vma_read_unlock(vma);
+
+	if (!(fault & VM_FAULT_RETRY)) {
+		count_vm_vma_lock_event(VMA_LOCK_SUCCESS);
+		goto done;
+	}
+	count_vm_vma_lock_event(VMA_LOCK_RETRY);
+
+	/* Quick path to respond to signals */
+	if (fault_signal_pending(fault, regs)) {
+		if (!user_mode(regs))
+			kernelmode_fixup_or_oops(regs, error_code, address,
+						 SIGBUS, BUS_ADRERR,
+						 ARCH_DEFAULT_PKEY);
+		return;
+	}
+lock_mmap:
+#endif /* CONFIG_PER_VMA_LOCK */
+
 	/*
 	 * Kernel-mode access to the user address space should only occur
 	 * on well-defined single instructions listed in the exception
@@ -1423,6 +1456,9 @@ void do_user_addr_fault(struct pt_regs *regs,
 	}
 
 	mmap_read_unlock(mm);
+#ifdef CONFIG_PER_VMA_LOCK
+done:
+#endif
 	if (likely(!(fault & VM_FAULT_ERROR)))
 		return;
 
-- 
2.37.2.789.g6183377224-goog


WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, joelaf@google.com, songliubraving@fb.com,
	mhocko@suse.com, david@redhat.com, peterz@infradead.org,
	bigeasy@linutronix.de, peterx@redhat.com, dhowells@redhat.com,
	linux-mm@kvack.org, jglisse@google.com, dave@stgolabs.net,
	minchan@google.com, x86@kernel.org, hughd@google.com,
	willy@infradead.org, laurent.dufour@fr.ibm.com, mgorman@suse.de,
	rientjes@google.com, axelrasmussen@google.com,
	kernel-team@android.com, paulmck@kernel.org,
	liam.howlett@oracle.com, luto@kernel.org, ldufour@linux.ibm.com,
	surenb@google.com, vbabka@suse.cz,
	linux-arm-kernel@lists.infradead.org, kent.overstreet@linux.dev,
	linux-kernel@vger.kernel.org, hannes@cmpxchg.org,
	linuxppc-dev@lists.ozlabs.org
Subject: [RFC PATCH RESEND 22/28] x86/mm: try VMA lock-based page fault handling first
Date: Thu,  1 Sep 2022 10:35:10 -0700	[thread overview]
Message-ID: <20220901173516.702122-23-surenb@google.com> (raw)
In-Reply-To: <20220901173516.702122-1-surenb@google.com>

Attempt VMA lock-based page fault handling first, and fall back to the
existing mmap_lock-based handling if that fails.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 arch/x86/mm/fault.c | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index fa71a5d12e87..35e74e3dc2c1 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -19,6 +19,7 @@
 #include <linux/uaccess.h>		/* faulthandler_disabled()	*/
 #include <linux/efi.h>			/* efi_crash_gracefully_on_page_fault()*/
 #include <linux/mm_types.h>
+#include <linux/mm.h>			/* find_and_lock_vma() */
 
 #include <asm/cpufeature.h>		/* boot_cpu_has, ...		*/
 #include <asm/traps.h>			/* dotraplinkage, ...		*/
@@ -1323,6 +1324,38 @@ void do_user_addr_fault(struct pt_regs *regs,
 	}
 #endif
 
+#ifdef CONFIG_PER_VMA_LOCK
+	if (!(flags & FAULT_FLAG_USER) || atomic_read(&mm->mm_users) == 1)
+		goto lock_mmap;
+
+	vma = find_and_lock_anon_vma(mm, address);
+	if (!vma)
+		goto lock_mmap;
+
+	if (unlikely(access_error(error_code, vma))) {
+		vma_read_unlock(vma);
+		goto lock_mmap;
+	}
+	fault = handle_mm_fault(vma, address, flags | FAULT_FLAG_VMA_LOCK, regs);
+	vma_read_unlock(vma);
+
+	if (!(fault & VM_FAULT_RETRY)) {
+		count_vm_vma_lock_event(VMA_LOCK_SUCCESS);
+		goto done;
+	}
+	count_vm_vma_lock_event(VMA_LOCK_RETRY);
+
+	/* Quick path to respond to signals */
+	if (fault_signal_pending(fault, regs)) {
+		if (!user_mode(regs))
+			kernelmode_fixup_or_oops(regs, error_code, address,
+						 SIGBUS, BUS_ADRERR,
+						 ARCH_DEFAULT_PKEY);
+		return;
+	}
+lock_mmap:
+#endif /* CONFIG_PER_VMA_LOCK */
+
 	/*
 	 * Kernel-mode access to the user address space should only occur
 	 * on well-defined single instructions listed in the exception
@@ -1423,6 +1456,9 @@ void do_user_addr_fault(struct pt_regs *regs,
 	}
 
 	mmap_read_unlock(mm);
+#ifdef CONFIG_PER_VMA_LOCK
+done:
+#endif
 	if (likely(!(fault & VM_FAULT_ERROR)))
 		return;
 
-- 
2.37.2.789.g6183377224-goog


WARNING: multiple messages have this Message-ID (diff)
From: Suren Baghdasaryan <surenb@google.com>
To: akpm@linux-foundation.org
Cc: michel@lespinasse.org, jglisse@google.com, mhocko@suse.com,
	vbabka@suse.cz,  hannes@cmpxchg.org, mgorman@suse.de,
	dave@stgolabs.net, willy@infradead.org,  liam.howlett@oracle.com,
	peterz@infradead.org, ldufour@linux.ibm.com,
	 laurent.dufour@fr.ibm.com, paulmck@kernel.org, luto@kernel.org,
	 songliubraving@fb.com, peterx@redhat.com, david@redhat.com,
	 dhowells@redhat.com, hughd@google.com, bigeasy@linutronix.de,
	 kent.overstreet@linux.dev, rientjes@google.com,
	axelrasmussen@google.com,  joelaf@google.com, minchan@google.com,
	surenb@google.com,  kernel-team@android.com, linux-mm@kvack.org,
	 linux-arm-kernel@lists.infradead.org,
	linuxppc-dev@lists.ozlabs.org,  x86@kernel.org,
	linux-kernel@vger.kernel.org
Subject: [RFC PATCH RESEND 22/28] x86/mm: try VMA lock-based page fault handling first
Date: Thu,  1 Sep 2022 10:35:10 -0700	[thread overview]
Message-ID: <20220901173516.702122-23-surenb@google.com> (raw)
In-Reply-To: <20220901173516.702122-1-surenb@google.com>

Attempt VMA lock-based page fault handling first, and fall back to the
existing mmap_lock-based handling if that fails.

Signed-off-by: Suren Baghdasaryan <surenb@google.com>
---
 arch/x86/mm/fault.c | 36 ++++++++++++++++++++++++++++++++++++
 1 file changed, 36 insertions(+)

diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
index fa71a5d12e87..35e74e3dc2c1 100644
--- a/arch/x86/mm/fault.c
+++ b/arch/x86/mm/fault.c
@@ -19,6 +19,7 @@
 #include <linux/uaccess.h>		/* faulthandler_disabled()	*/
 #include <linux/efi.h>			/* efi_crash_gracefully_on_page_fault()*/
 #include <linux/mm_types.h>
+#include <linux/mm.h>			/* find_and_lock_vma() */
 
 #include <asm/cpufeature.h>		/* boot_cpu_has, ...		*/
 #include <asm/traps.h>			/* dotraplinkage, ...		*/
@@ -1323,6 +1324,38 @@ void do_user_addr_fault(struct pt_regs *regs,
 	}
 #endif
 
+#ifdef CONFIG_PER_VMA_LOCK
+	if (!(flags & FAULT_FLAG_USER) || atomic_read(&mm->mm_users) == 1)
+		goto lock_mmap;
+
+	vma = find_and_lock_anon_vma(mm, address);
+	if (!vma)
+		goto lock_mmap;
+
+	if (unlikely(access_error(error_code, vma))) {
+		vma_read_unlock(vma);
+		goto lock_mmap;
+	}
+	fault = handle_mm_fault(vma, address, flags | FAULT_FLAG_VMA_LOCK, regs);
+	vma_read_unlock(vma);
+
+	if (!(fault & VM_FAULT_RETRY)) {
+		count_vm_vma_lock_event(VMA_LOCK_SUCCESS);
+		goto done;
+	}
+	count_vm_vma_lock_event(VMA_LOCK_RETRY);
+
+	/* Quick path to respond to signals */
+	if (fault_signal_pending(fault, regs)) {
+		if (!user_mode(regs))
+			kernelmode_fixup_or_oops(regs, error_code, address,
+						 SIGBUS, BUS_ADRERR,
+						 ARCH_DEFAULT_PKEY);
+		return;
+	}
+lock_mmap:
+#endif /* CONFIG_PER_VMA_LOCK */
+
 	/*
 	 * Kernel-mode access to the user address space should only occur
 	 * on well-defined single instructions listed in the exception
@@ -1423,6 +1456,9 @@ void do_user_addr_fault(struct pt_regs *regs,
 	}
 
 	mmap_read_unlock(mm);
+#ifdef CONFIG_PER_VMA_LOCK
+done:
+#endif
 	if (likely(!(fault & VM_FAULT_ERROR)))
 		return;
 
-- 
2.37.2.789.g6183377224-goog


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-09-01 17:38 UTC|newest]

Thread overview: 273+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 17:34 [RFC PATCH RESEND 00/28] per-VMA locks proposal Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 01/28] mm: introduce CONFIG_PER_VMA_LOCK Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 02/28] mm: rcu safe VMA freeing Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 03/28] mm: introduce __find_vma to be used without mmap_lock protection Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 20:22   ` Kent Overstreet
2022-09-01 20:22     ` Kent Overstreet
2022-09-01 20:22     ` Kent Overstreet
2022-09-01 23:18     ` Suren Baghdasaryan
2022-09-01 23:18       ` Suren Baghdasaryan
2022-09-01 23:18       ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 04/28] mm: move mmap_lock assert function definitions Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 20:24   ` Kent Overstreet
2022-09-01 20:24     ` Kent Overstreet
2022-09-01 20:24     ` Kent Overstreet
2022-09-01 20:51     ` Liam Howlett
2022-09-01 20:51       ` Liam Howlett
2022-09-01 20:51       ` Liam Howlett
2022-09-01 23:21       ` Suren Baghdasaryan
2022-09-01 23:21         ` Suren Baghdasaryan
2022-09-01 23:21         ` Suren Baghdasaryan
2022-09-02  6:23     ` Sebastian Andrzej Siewior
2022-09-02  6:23       ` Sebastian Andrzej Siewior
2022-09-02  6:23       ` Sebastian Andrzej Siewior
2022-09-02 17:46       ` Suren Baghdasaryan
2022-09-02 17:46         ` Suren Baghdasaryan
2022-09-02 17:46         ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 05/28] mm: add per-VMA lock and helper functions to control it Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-06 13:46   ` Laurent Dufour
2022-09-06 13:46     ` Laurent Dufour
2022-09-06 13:46     ` Laurent Dufour
2022-09-06 17:24     ` Suren Baghdasaryan
2022-09-06 17:24       ` Suren Baghdasaryan
2022-09-06 17:24       ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 06/28] mm: mark VMA as locked whenever vma->vm_flags are modified Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-06 14:26   ` Laurent Dufour
2022-09-06 14:26     ` Laurent Dufour
2022-09-06 14:26     ` Laurent Dufour
2022-09-06 19:00     ` Suren Baghdasaryan
2022-09-06 19:00       ` Suren Baghdasaryan
2022-09-06 19:00       ` Suren Baghdasaryan
2022-09-06 20:00       ` Liam Howlett
2022-09-06 20:00         ` Liam Howlett
2022-09-06 20:00         ` Liam Howlett
2022-09-06 20:13         ` Suren Baghdasaryan
2022-09-06 20:13           ` Suren Baghdasaryan
2022-09-06 20:13           ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 07/28] kernel/fork: mark VMAs as locked before copying pages during fork Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-06 14:37   ` Laurent Dufour
2022-09-06 14:37     ` Laurent Dufour
2022-09-06 14:37     ` Laurent Dufour
2022-09-08 23:57     ` Suren Baghdasaryan
2022-09-08 23:57       ` Suren Baghdasaryan
2022-09-08 23:57       ` Suren Baghdasaryan
2022-09-09 13:27       ` Laurent Dufour
2022-09-09 13:27         ` Laurent Dufour
2022-09-09 13:27         ` Laurent Dufour
2022-09-09 16:29         ` Suren Baghdasaryan
2022-09-09 16:29           ` Suren Baghdasaryan
2022-09-09 16:29           ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 08/28] mm/khugepaged: mark VMA as locked while collapsing a hugepage Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-06 14:43   ` Laurent Dufour
2022-09-06 14:43     ` Laurent Dufour
2022-09-06 14:43     ` Laurent Dufour
2022-09-09  0:15     ` Suren Baghdasaryan
2022-09-09  0:15       ` Suren Baghdasaryan
2022-09-09  0:15       ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 09/28] mm/mempolicy: mark VMA as locked when changing protection policy Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-06 14:47   ` Laurent Dufour
2022-09-06 14:47     ` Laurent Dufour
2022-09-06 14:47     ` Laurent Dufour
2022-09-09  0:27     ` Suren Baghdasaryan
2022-09-09  0:27       ` Suren Baghdasaryan
2022-09-09  0:27       ` Suren Baghdasaryan
2022-09-01 17:34 ` [RFC PATCH RESEND 10/28] mm/mmap: mark VMAs as locked in vma_adjust Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-06 15:35   ` Laurent Dufour
2022-09-06 15:35     ` Laurent Dufour
2022-09-06 15:35     ` Laurent Dufour
2022-09-09  0:51     ` Suren Baghdasaryan
2022-09-09  0:51       ` Suren Baghdasaryan
2022-09-09  0:51       ` Suren Baghdasaryan
2022-09-09 15:52       ` Laurent Dufour
2022-09-09 15:52         ` Laurent Dufour
2022-09-09 15:52         ` Laurent Dufour
2022-09-01 17:34 ` [RFC PATCH RESEND 11/28] mm/mmap: mark VMAs as locked before merging or splitting them Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-01 17:34   ` Suren Baghdasaryan
2022-09-06 15:44   ` Laurent Dufour
2022-09-06 15:44     ` Laurent Dufour
2022-09-06 15:44     ` Laurent Dufour
2022-09-01 17:35 ` [RFC PATCH RESEND 12/28] mm/mremap: mark VMA as locked while remapping it to a new address range Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-06 16:09   ` Laurent Dufour
2022-09-06 16:09     ` Laurent Dufour
2022-09-06 16:09     ` Laurent Dufour
2022-09-01 17:35 ` [RFC PATCH RESEND 13/28] mm: conditionally mark VMA as locked in free_pgtables and unmap_page_range Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 10:33   ` Laurent Dufour
2022-09-09 10:33     ` Laurent Dufour
2022-09-09 10:33     ` Laurent Dufour
2022-09-09 16:43     ` Suren Baghdasaryan
2022-09-09 16:43       ` Suren Baghdasaryan
2022-09-09 16:43       ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 14/28] mm: mark VMAs as locked before isolating them Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 13:35   ` Laurent Dufour
2022-09-09 13:35     ` Laurent Dufour
2022-09-09 13:35     ` Laurent Dufour
2022-09-09 16:28     ` Suren Baghdasaryan
2022-09-09 16:28       ` Suren Baghdasaryan
2022-09-09 16:28       ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 15/28] mm/mmap: mark adjacent VMAs as locked if they can grow into unmapped area Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 13:43   ` Laurent Dufour
2022-09-09 13:43     ` Laurent Dufour
2022-09-09 13:43     ` Laurent Dufour
2022-09-09 16:25     ` Suren Baghdasaryan
2022-09-09 16:25       ` Suren Baghdasaryan
2022-09-09 16:25       ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 16/28] kernel/fork: assert no VMA readers during its destruction Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 13:56   ` Laurent Dufour
2022-09-09 13:56     ` Laurent Dufour
2022-09-09 13:56     ` Laurent Dufour
2022-09-09 16:19     ` Suren Baghdasaryan
2022-09-09 16:19       ` Suren Baghdasaryan
2022-09-09 16:19       ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 17/28] mm/mmap: prevent pagefault handler from racing with mmu_notifier registration Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 14:20   ` Laurent Dufour
2022-09-09 14:20     ` Laurent Dufour
2022-09-09 14:20     ` Laurent Dufour
2022-09-09 16:12     ` Suren Baghdasaryan
2022-09-09 16:12       ` Suren Baghdasaryan
2022-09-09 16:12       ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 18/28] mm: add FAULT_FLAG_VMA_LOCK flag Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 14:26   ` Laurent Dufour
2022-09-09 14:26     ` Laurent Dufour
2022-09-09 14:26     ` Laurent Dufour
2022-09-01 17:35 ` [RFC PATCH RESEND 19/28] mm: disallow do_swap_page to handle page faults under VMA lock Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-06 19:39   ` Peter Xu
2022-09-06 19:39     ` Peter Xu
2022-09-06 19:39     ` Peter Xu
2022-09-06 20:08     ` Suren Baghdasaryan
2022-09-06 20:08       ` Suren Baghdasaryan
2022-09-06 20:08       ` Suren Baghdasaryan
2022-09-06 20:22       ` Peter Xu
2022-09-06 20:22         ` Peter Xu
2022-09-06 20:22         ` Peter Xu
2022-09-07  0:58         ` Suren Baghdasaryan
2022-09-07  0:58           ` Suren Baghdasaryan
2022-09-07  0:58           ` Suren Baghdasaryan
2022-09-09 14:26   ` Laurent Dufour
2022-09-09 14:26     ` Laurent Dufour
2022-09-09 14:26     ` Laurent Dufour
2022-09-01 17:35 ` [RFC PATCH RESEND 20/28] mm: introduce per-VMA lock statistics Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 14:28   ` Laurent Dufour
2022-09-09 14:28     ` Laurent Dufour
2022-09-09 14:28     ` Laurent Dufour
2022-09-09 16:11     ` Suren Baghdasaryan
2022-09-09 16:11       ` Suren Baghdasaryan
2022-09-09 16:11       ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 21/28] mm: introduce find_and_lock_anon_vma to be used from arch-specific code Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 14:38   ` Laurent Dufour
2022-09-09 14:38     ` Laurent Dufour
2022-09-09 14:38     ` Laurent Dufour
2022-09-09 16:10     ` Suren Baghdasaryan
2022-09-09 16:10       ` Suren Baghdasaryan
2022-09-09 16:10       ` Suren Baghdasaryan
2022-09-01 17:35 ` Suren Baghdasaryan [this message]
2022-09-01 17:35   ` [RFC PATCH RESEND 22/28] x86/mm: try VMA lock-based page fault handling first Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 23/28] x86/mm: define ARCH_SUPPORTS_PER_VMA_LOCK Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 20:20   ` Kent Overstreet
2022-09-01 20:20     ` Kent Overstreet
2022-09-01 20:20     ` Kent Overstreet
2022-09-01 23:17     ` Suren Baghdasaryan
2022-09-01 23:17       ` Suren Baghdasaryan
2022-09-01 23:17       ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 24/28] arm64/mm: try VMA lock-based page fault handling first Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 25/28] arm64/mm: define ARCH_SUPPORTS_PER_VMA_LOCK Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 26/28] powerc/mm: try VMA lock-based page fault handling first Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 27/28] powerpc/mm: define ARCH_SUPPORTS_PER_VMA_LOCK Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35 ` [RFC PATCH RESEND 28/28] kernel/fork: throttle call_rcu() calls in vm_area_free Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-01 17:35   ` Suren Baghdasaryan
2022-09-09 15:19   ` Laurent Dufour
2022-09-09 15:19     ` Laurent Dufour
2022-09-09 15:19     ` Laurent Dufour
2022-09-09 16:02     ` Suren Baghdasaryan
2022-09-09 16:02       ` Suren Baghdasaryan
2022-09-09 16:02       ` Suren Baghdasaryan
2022-09-09 16:14       ` Laurent Dufour
2022-09-09 16:14         ` Laurent Dufour
2022-09-09 16:14         ` Laurent Dufour
2022-09-01 20:58 ` [RFC PATCH RESEND 00/28] per-VMA locks proposal Kent Overstreet
2022-09-01 20:58   ` Kent Overstreet
2022-09-01 20:58   ` Kent Overstreet
2022-09-01 23:26   ` Suren Baghdasaryan
2022-09-01 23:26     ` Suren Baghdasaryan
2022-09-01 23:26     ` Suren Baghdasaryan
2022-09-11  9:35     ` Vlastimil Babka
2022-09-11  9:35       ` Vlastimil Babka
2022-09-11  9:35       ` Vlastimil Babka
2022-09-28  2:28       ` Suren Baghdasaryan
2022-09-28  2:28         ` Suren Baghdasaryan
2022-09-28  2:28         ` Suren Baghdasaryan
2022-09-29 11:18         ` Vlastimil Babka
2022-09-29 11:18           ` Vlastimil Babka
2022-09-29 11:18           ` Vlastimil Babka
2022-09-02  7:42 ` Peter Zijlstra
2022-09-02  7:42   ` Peter Zijlstra
2022-09-02  7:42   ` Peter Zijlstra
2022-09-02 14:45   ` Suren Baghdasaryan
2022-09-02 14:45     ` Suren Baghdasaryan
2022-09-02 14:45     ` Suren Baghdasaryan
2022-09-05 12:32 ` Michal Hocko
2022-09-05 12:32   ` Michal Hocko
2022-09-05 12:32   ` Michal Hocko
2022-09-05 18:32   ` Suren Baghdasaryan
2022-09-05 18:32     ` Suren Baghdasaryan
2022-09-05 18:32     ` Suren Baghdasaryan
2022-09-05 20:35     ` Kent Overstreet
2022-09-05 20:35       ` Kent Overstreet
2022-09-05 20:35       ` Kent Overstreet
2022-09-06 15:46       ` Suren Baghdasaryan
2022-09-06 15:46         ` Suren Baghdasaryan
2022-09-06 15:46         ` Suren Baghdasaryan

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=20220901173516.702122-23-surenb@google.com \
    --to=surenb@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=bigeasy@linutronix.de \
    --cc=dave@stgolabs.net \
    --cc=david@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jglisse@google.com \
    --cc=joelaf@google.com \
    --cc=kent.overstreet@linux.dev \
    --cc=kernel-team@android.com \
    --cc=laurent.dufour@fr.ibm.com \
    --cc=ldufour@linux.ibm.com \
    --cc=liam.howlett@oracle.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luto@kernel.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.com \
    --cc=michel@lespinasse.org \
    --cc=minchan@google.com \
    --cc=paulmck@kernel.org \
    --cc=peterx@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rientjes@google.com \
    --cc=songliubraving@fb.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.org \
    --cc=x86@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.