Re: [PATCH] drm/radeon: TTM must be init with cpu-visible VRAM, v2

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Mar 1, 2014 at 5:56 AM, Christian König <deathsimple@xxxxxxxxxxx> wrote:
> Am 28.02.2014 19:50, schrieb Lauri Kasanen:
>
>> Without this, a bo may get created in the cpu-inaccessible vram.
>> Before the CP engines get setup, all copies are done via cpu memcpy.
>>
>> This means that the cpu tries to read from inaccessible memory, fails,
>> and the radeon module proceeds to disable acceleration.
>>
>> Doing this has no downsides, as the real VRAM size gets set as soon as the
>> CP engines get init.
>>
>> This is a candidate for 3.14 fixes.
>>
>> v2: Add comment on why the function is used
>>
>> Signed-off-by: Lauri Kasanen <cand@xxxxxxx>
>
>
> Reviewed-by: Christian König <christian.koenig@xxxxxxx>
>
> And I suggest to add "Cc: stable@xxxxxxxxxxxxxxx" as well.
>
> Christian.

Won't this create objects that are stuck in the middle of VRAM with
the new top down approach?

then when we go to use all the VRAM they'll be pinned in the middle?

Dave.
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/dri-devel





[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux