Displaying 2 results from an estimated 2 matches for "nvkm_ramht_new".
2015 Dec 20
8
[Bug 93458] New: page allocation failure: order:5, mode:0x240c0c0
...lt;ffffffff8114d2c4>] warn_alloc_failed+0xd4/0x120
[<ffffffff8114f853>] __alloc_pages_nodemask+0x103/0x780
[<ffffffff811500d2>] alloc_kmem_pages+0x12/0x20
[<ffffffff81161a03>] kmalloc_order+0x13/0x40
[<ffffffff8117a517>] __kmalloc+0xb7/0xf0
[<ffffffff813e87b0>] nvkm_ramht_new+0x40/0xf0
[<ffffffff8144ff40>] g84_fifo_chan_ctor+0x140/0x170
[<ffffffff81451b87>] g84_fifo_gpfifo_new+0xc7/0x300
[<ffffffff8143c366>] ? nvkm_disp_class_get+0x26/0x60
[<ffffffff81449d02>] nvkm_fifo_class_new+0x12/0x20
[<ffffffff8143baf1>] nvkm_udevice_child_new+0x...
2016 Mar 06
0
[PATCH] core: use vzalloc for allocating ramht
Most calls to nvkm_ramht_new use 0x8000 as the size. This results in a
fairly sizeable chunk of memory to be allocated, which may not be
available with kzalloc. Since this is done fairly rarely (once per
channel), use vzalloc instead.
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
drm/nouveau/nvkm/core/ramht....