Applied. Thanks!
On Mon, Apr 7, 2025 at 10:42 AM Christian König
wrote:
>
> Am 07.04.25 um 16:18 schrieb Matthew Auld:
> > The page_link lower bits of the first sg could contain something like
> > SG_END, if we are mapping a single VRAM page or contiguous blob which
> > fits into one sg entry. R
On 07/04/2025 15:46, Christian König wrote:
Am 07.04.25 um 16:44 schrieb Matthew Auld:
On 07/04/2025 15:32, Christian König wrote:
Am 07.04.25 um 16:18 schrieb Matthew Auld:
The page_link lower bits of the first sg could contain something like
SG_END, if we are mapping a single VRAM page or co
Am 07.04.25 um 16:44 schrieb Matthew Auld:
> On 07/04/2025 15:32, Christian König wrote:
>> Am 07.04.25 um 16:18 schrieb Matthew Auld:
>>> The page_link lower bits of the first sg could contain something like
>>> SG_END, if we are mapping a single VRAM page or contiguous blob which
>>> fits into on
On 07/04/2025 15:32, Christian König wrote:
Am 07.04.25 um 16:18 schrieb Matthew Auld:
The page_link lower bits of the first sg could contain something like
SG_END, if we are mapping a single VRAM page or contiguous blob which
fits into one sg entry. Rather pull out the struct page, and use that
Am 07.04.25 um 16:18 schrieb Matthew Auld:
> The page_link lower bits of the first sg could contain something like
> SG_END, if we are mapping a single VRAM page or contiguous blob which
> fits into one sg entry. Rather pull out the struct page, and use that in
> our check to know if we mapped stru
The page_link lower bits of the first sg could contain something like
SG_END, if we are mapping a single VRAM page or contiguous blob which
fits into one sg entry. Rather pull out the struct page, and use that in
our check to know if we mapped struct pages vs VRAM.
Fixes: f44ffd677fb3 ("drm/amdgpu
