[Mesa-dev] [PATCH 1/3] gm107/ir: Emit SV_CLOCK system value
Ilia Mirkin
imirkin at alum.mit.edu
Fri Mar 31 03:21:06 UTC 2017
Did you check what the blob does? There's clocklo/hi and
globaltimerlo/hi. Without additional documentation, it's a bit hard to
tell the difference... Note that envydis's gf100.c/gk110.c disagree on
which is which. Probably not due to any architectural reasons, but due
to RE methodology. (From before nvdisasm was
available/trusted/used/whatever.)
On Thu, Mar 30, 2017 at 10:33 PM, Boyan Ding <boyan.j.ding at gmail.com> wrote:
> Signed-off-by: Boyan Ding <boyan.j.ding at gmail.com>
> ---
> src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp
> index 6de3f396e3..ab9c94b4d0 100644
> --- a/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp
> +++ b/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gm107.cpp
> @@ -269,6 +269,7 @@ CodeEmitterGM107::emitSYS(int pos, const Value *val)
> case SV_INVOCATION_INFO: id = 0x1d; break;
> case SV_TID : id = 0x21 + val->reg.data.sv.index; break;
> case SV_CTAID : id = 0x25 + val->reg.data.sv.index; break;
> + case SV_CLOCK : id = 0x50 + val->reg.data.sv.index; break;
> default:
> assert(!"invalid system value");
> id = 0;
> --
> 2.12.0
>
> _______________________________________________
> mesa-dev mailing list
> mesa-dev at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-dev
More information about the mesa-dev
mailing list