Displaying 2 results from an estimated 2 matches for "bf066358".
2015 Nov 11
1
[PATCH] instmem/gk20a: fix race conditions
...t; currently using a given instobj.
> Out of curiosity, which instobjs are being accessed concurrently?
PGTs it seems - at least this is what dumping a stack when detecting a
concurrent usage on an instobj indicates:
[ 270.547052] [<bf0618dc>] (gk20a_instobj_acquire [nouveau]) from
[<bf066358>] (gf100_vm_map_sg+0x58/0x124 [nouveau])
[ 270.557568] [<bf066358>] (gf100_vm_map_sg [nouveau]) from
[<bf0641b0>] (nvkm_vm_map+0x300/0x3bc [nouveau])
[ 270.567333] [<bf0641b0>] (nvkm_vm_map [nouveau]) from [<bf0bcbd4>]
(nouveau_bo_vma_add+0x74/0xa0 [nouveau])
[ 270.577...
2015 Nov 09
2
[PATCH] instmem/gk20a: fix race conditions
The LRU list used for recycling CPU mappings was handling concurrency
very poorly. For instance, if an instobj was acquired twice before being
released once, it would end up into the LRU list even though there is
still a client accessing it.
This patch fixes this by properly counting how many clients are
currently using a given instobj.
While at it, we also raise errors when inconsistencies are