Re: [PATCH 1/3] drm/amdkfd: classify and map mixed svm range pages in GPU

Am 2021-05-17 um 9:44 a.m. schrieb Felix Kuehling: > A few more comments inline. Sorry I took so long. > > Am 2021-05-12 um 1:34 p.m. schrieb Alex Sierra: > >> [Why] >> svm ranges can have mixed pages from device or system memory. >> A good example is, after a prange has been allocated in VRAM

Re: [PATCH 1/3] drm/amdkfd: classify and map mixed svm range pages in GPU

A few more comments inline. Sorry I took so long. Am 2021-05-12 um 1:34 p.m. schrieb Alex Sierra: > [Why] > svm ranges can have mixed pages from device or system memory. > A good example is, after a prange has been allocated in VRAM and a > copy-on-write is triggered by a fork. This invalidates

[PATCH 1/3] drm/amdkfd: classify and map mixed svm range pages in GPU

[Why] svm ranges can have mixed pages from device or system memory. A good example is, after a prange has been allocated in VRAM and a copy-on-write is triggered by a fork. This invalidates some pages inside the prange. Endding up in mixed pages. [How] By classifying each page inside a prange,