Displaying 3 results from an estimated 3 matches for "9b3dcb81be5f".
2020 Jul 20
1
[PATCH v2 3/5] mm/notifier: add migration invalidation type
...ge,
> range->start = start;
> range->end = end;
> range->flags = flags;
> + range->migrate_pgmap_owner = NULL;
> }
>
> #define ptep_clear_flush_young_notify(__vma, __address, __ptep) \
> diff --git a/mm/migrate.c b/mm/migrate.c
> index 2bbc5c4c672e..9b3dcb81be5f 100644
> +++ b/mm/migrate.c
> @@ -2391,8 +2391,14 @@ static void migrate_vma_collect(struct migrate_vma *migrate)
> {
> struct mmu_notifier_range range;
>
> - mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, NULL,
> + /*
> + * Note that the src_owner is passed...
2020 Jul 13
0
[PATCH v2 3/5] mm/notifier: add migration invalidation type
...ier_range_init(struct mmu_notifier_range *range,
range->start = start;
range->end = end;
range->flags = flags;
+ range->migrate_pgmap_owner = NULL;
}
#define ptep_clear_flush_young_notify(__vma, __address, __ptep) \
diff --git a/mm/migrate.c b/mm/migrate.c
index 2bbc5c4c672e..9b3dcb81be5f 100644
--- a/mm/migrate.c
+++ b/mm/migrate.c
@@ -2391,8 +2391,14 @@ static void migrate_vma_collect(struct migrate_vma *migrate)
{
struct mmu_notifier_range range;
- mmu_notifier_range_init(&range, MMU_NOTIFY_CLEAR, 0, NULL,
+ /*
+ * Note that the src_owner is passed to the mmu notifier c...
2020 Jul 13
9
[PATCH v2 0/5] mm/migrate: avoid device private invalidations
The goal for this series is to avoid device private memory TLB
invalidations when migrating a range of addresses from system
memory to device private memory and some of those pages have already
been migrated. The approach taken is to introduce a new mmu notifier
invalidation event type and use that in the device driver to skip
invalidation callbacks from migrate_vma_setup(). The device driver is