Displaying 7 results from an estimated 7 matches for "_from_device_".
2020 Jul 20
2
[PATCH v2 2/5] mm/migrate: add a direction parameter to migrate_vma
...; > @@ -180,6 +180,11 @@ static inline unsigned long migrate_pfn(unsigned long pfn)
> > > return (pfn << MIGRATE_PFN_SHIFT) | MIGRATE_PFN_VALID;
> > > }
> > > +enum migrate_vma_direction {
> > > + MIGRATE_VMA_FROM_SYSTEM,
> > > + MIGRATE_VMA_FROM_DEVICE_PRIVATE,
> > > +};
> >
> > I would have guessed this is more natural as _FROM_DEVICE_ and
> > TO_DEVICE_ ?
>
> The caller controls where the destination memory is allocated so it isn't
> necessarily device private memory, it could be from system to system.
&...
2020 Jul 20
2
[PATCH v2 2/5] mm/migrate: add a direction parameter to migrate_vma
.../*
> * We come here with mmap_lock write lock held just for
> @@ -578,6 +579,7 @@ kvmppc_svm_page_out(struct vm_area_struct *vma, unsigned long start,
> mig.src = &src_pfn;
> mig.dst = &dst_pfn;
> mig.src_owner = &kvmppc_uvmem_pgmap;
> + mig.dir = MIGRATE_VMA_FROM_DEVICE_PRIVATE;
>
> mutex_lock(&kvm->arch.uvmem_lock);
> /* The requested page is already paged-out, nothing to do */
> diff --git a/drivers/gpu/drm/nouveau/nouveau_dmem.c b/drivers/gpu/drm/nouveau/nouveau_dmem.c
> index e5c230d9ae24..e5c83b8ee82e 100644
> +++ b/drivers/gpu/d...
2020 Jul 20
1
[PATCH v2 2/5] mm/migrate: add a direction parameter to migrate_vma
...ong migrate_pfn(unsigned long pfn)
> > > > > return (pfn << MIGRATE_PFN_SHIFT) | MIGRATE_PFN_VALID;
> > > > > }
> > > > > +enum migrate_vma_direction {
> > > > > + MIGRATE_VMA_FROM_SYSTEM,
> > > > > + MIGRATE_VMA_FROM_DEVICE_PRIVATE,
> > > > > +};
> > > >
> > > > I would have guessed this is more natural as _FROM_DEVICE_ and
> > > > TO_DEVICE_ ?
> > >
> > > The caller controls where the destination memory is allocated so it isn't
> > > n...
2020 Jul 20
0
[PATCH v2 2/5] mm/migrate: add a direction parameter to migrate_vma
...80,6 +180,11 @@ static inline unsigned long migrate_pfn(unsigned long pfn)
>>>> return (pfn << MIGRATE_PFN_SHIFT) | MIGRATE_PFN_VALID;
>>>> }
>>>> +enum migrate_vma_direction {
>>>> + MIGRATE_VMA_FROM_SYSTEM,
>>>> + MIGRATE_VMA_FROM_DEVICE_PRIVATE,
>>>> +};
>>>
>>> I would have guessed this is more natural as _FROM_DEVICE_ and
>>> TO_DEVICE_ ?
>>
>> The caller controls where the destination memory is allocated so it isn't
>> necessarily device private memory, it could be fro...
2020 Jul 20
0
[PATCH v2 2/5] mm/migrate: add a direction parameter to migrate_vma
...here with mmap_lock write lock held just for
>> @@ -578,6 +579,7 @@ kvmppc_svm_page_out(struct vm_area_struct *vma, unsigned long start,
>> mig.src = &src_pfn;
>> mig.dst = &dst_pfn;
>> mig.src_owner = &kvmppc_uvmem_pgmap;
>> + mig.dir = MIGRATE_VMA_FROM_DEVICE_PRIVATE;
>>
>> mutex_lock(&kvm->arch.uvmem_lock);
>> /* The requested page is already paged-out, nothing to do */
>> diff --git a/drivers/gpu/drm/nouveau/nouveau_dmem.c b/drivers/gpu/drm/nouveau/nouveau_dmem.c
>> index e5c230d9ae24..e5c83b8ee82e 100644
&...
2020 Jul 20
0
[PATCH v2 2/5] mm/migrate: add a direction parameter to migrate_vma
...g migrate_pfn(unsigned long pfn)
>>>>>> return (pfn << MIGRATE_PFN_SHIFT) | MIGRATE_PFN_VALID;
>>>>>> }
>>>>>> +enum migrate_vma_direction {
>>>>>> + MIGRATE_VMA_FROM_SYSTEM,
>>>>>> + MIGRATE_VMA_FROM_DEVICE_PRIVATE,
>>>>>> +};
>>>>>
>>>>> I would have guessed this is more natural as _FROM_DEVICE_ and
>>>>> TO_DEVICE_ ?
>>>>
>>>> The caller controls where the destination memory is allocated so it isn't
>>>...
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