On 2019-01-07 9:21 a.m., Christian König wrote:
> Am 14.12.18 um 22:10 schrieb Yang, Philip:
>> Use HMM helper function hmm_vma_fault() to get physical pages backing
>> userptr and start CPU page table update track of those pages. Then use
>> hmm_vma_range_done() to check if those pages are updat
Am 14.12.18 um 22:10 schrieb Yang, Philip:
Use HMM helper function hmm_vma_fault() to get physical pages backing
userptr and start CPU page table update track of those pages. Then use
hmm_vma_range_done() to check if those pages are updated before
amdgpu_cs_submit for gfx or before user queues ar
I'm just getting up to speed again after winter vacation and have tons
of mails to dig through and a few important personal appointments coming
as well.
From skimming over it looks like it should work, but please give me at
least till Monday to take a closer look.
Christian.
Am 02.01.19 um
Hi Christian,
May you help review the CS parts related changes? I tested it using
libdrm Userptr Test under X. Do you know other test applications which
can stress the CS userptr path?
Thanks,
Philip
On 2018-12-14 4:25 p.m., Kuehling, Felix wrote:
> Except for the GEM and CS parts, the series
Except for the GEM and CS parts, the series is Reviewed-by: Felix
Kuehling
Regards,
Felix
On 2018-12-14 4:10 p.m., Yang, Philip wrote:
> Use HMM helper function hmm_vma_fault() to get physical pages backing
> userptr and start CPU page table update track of those pages. Then use
> hmm_vma_rang
Use HMM helper function hmm_vma_fault() to get physical pages backing
userptr and start CPU page table update track of those pages. Then use
hmm_vma_range_done() to check if those pages are updated before
amdgpu_cs_submit for gfx or before user queues are resumed for kfd.
If userptr pages are upda
