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

Am 2021-05-05 um 6:59 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 some pages > inside the prange. Endding up in mixed

[PATCH 3/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, bas

[PATCH 3/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, bas