Displaying 4 results from an estimated 4 matches for "unaligned_mem_access".
2015 Sep 30
2
Documentation request for MP warp error 0x10
...VALID_OPCODE"/>
<value value="13" name="GPR_OUT_OF_BOUNDS"/>
<value value="14" name="MEM_OUT_OF_BOUNDS"/>
<value value="17" name="INVALID_PARAM"/>
</bitfield>
</reg32>
[Additionally it seems like 15 = UNALIGNED_MEM_ACCESS]
It seems to happen whenever I try to access global memory on kepler
(potentially only atomics, not sure at this point). Knowing precisely
what causes the error to get triggered (and esp what we need to do in
order not to trigger it) would be most useful.
For reference, my shader looks something...
2015 Oct 02
2
Documentation request for MP warp error 0x10
...; name="GPR_OUT_OF_BOUNDS"/>
>> <value value="14" name="MEM_OUT_OF_BOUNDS"/>
>> <value value="17" name="INVALID_PARAM"/>
>> </bitfield>
>> </reg32>
>>
>> [Additionally it seems like 15 = UNALIGNED_MEM_ACCESS]
>>
>> It seems to happen whenever I try to access global memory on kepler
>> (potentially only atomics, not sure at this point). Knowing precisely
>> what causes the error to get triggered (and esp what we need to do in
>> order not to trigger it) would be most useful...
2015 Oct 07
1
[PATCH 1/2] gr: document mp error 0x10
...r/gf100.c
index f1358a5..dda7a7d 100644
--- a/drm/nouveau/nvkm/engine/gr/gf100.c
+++ b/drm/nouveau/nvkm/engine/gr/gf100.c
@@ -882,6 +882,7 @@ static const struct nvkm_enum gf100_mp_warp_error[] = {
{ 0x0d, "GPR_OUT_OF_BOUNDS" },
{ 0x0e, "MEM_OUT_OF_BOUNDS" },
{ 0x0f, "UNALIGNED_MEM_ACCESS" },
+ { 0x10, "INVALID_ADDR_SPACE" },
{ 0x11, "INVALID_PARAM" },
{}
};
--
2.4.9
2015 Oct 02
0
Documentation request for MP warp error 0x10
..."/>
> >> <value value="14" name="MEM_OUT_OF_BOUNDS"/>
> >> <value value="17" name="INVALID_PARAM"/>
> >> </bitfield>
> >> </reg32>
> >>
> >> [Additionally it seems like 15 = UNALIGNED_MEM_ACCESS]
> >>
> >> It seems to happen whenever I try to access global memory on kepler
> >> (potentially only atomics, not sure at this point). Knowing precisely
> >> what causes the error to get triggered (and esp what we need to do in
> >> order not to trigger...