search for: envydi

...at to decode a gm107 op, one has to supply sched bytes first. However we're nowhere as picky as nvdisasm - zeroes work just fine. --- mwk - this is a little hacky, but seemed like the simplest way to go. Please have a look and let me know if this is OK as is or if I should change it somehow. envydis/core-as.c | 2 +- envydis/core-dis.c | 5 ++++- envydis/gm107.c | 18 ++++++++++++++++-- include/dis.h | 3 +++ 4 files changed, 24 insertions(+), 4 deletions(-) diff --git a/envydis/core-as.c b/envydis/core-as.c index ce87653..ee9cd21 100644 --- a/envydis/core-as.c +++ b/envydis/core...

...nown: 00000000 c0800000] [unknown instruction] Into: 00000010: 001c0001 c38001ff add rn f64 $r0d $r0d 0x3fe0000000000000 The machine-code in question disassembles to the same using nvdisasm and works properly on an actual gpu. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- envydis/gk110.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/envydis/gk110.c b/envydis/gk110.c index 9af18e1..4790533 100644 --- a/envydis/gk110.c +++ b/envydis/gk110.c @@ -1274,6 +1274,7 @@ static struct insn tabcctlmod[] = { * 000000007f800000 2nd src * 0000003fff800000 2nd src (immediate)...

Op 11-01-15 om 01:34 schreef Ilia Mirkin: > And you're allowing saturate/neg emission on the short form. Yes > Is this already in envytools? Tesla floating point instructions are poorly documented in the RST documents; fmad is no exception. I'll make sure to check envydis. > Also, what's the shortForm thing? Documented in envytools; see http://envytools.readthedocs.org/en/latest/hw/graph/tesla/cuda/isa.html#instruction-format . In short, opcodes are either 4 bytes (short) or 8 bytes (long). > This change is > probably fine, but the changelog needs wo...

Hi, I think a nice project would be to write an application to figure out those latencies automatically maybe even based on envydis. It could generate latency information based on thread count, register usage, instruction/instruction class, hw unit used. Or even tries to figure out what kind of units exist. Like instructions out of a group which are free to issue/execute after instructions out of another one. I could imagine...

...$r3 0x3fe00000 (8) 3: add f64 $r0d $r0d $r2d (8) Into: 1: add f64 $r0d $r0d 0.500000 (8) This has been tested with the 2 double shader tests which I just send to the piglet list. On a gk208 (gk110 / SM35) card, and by checking the output of nouveau_compiler with both nvdisasm and envydis on gf100 / gk104 / gm107. Regards, Hans

...add f64 $r0d $r0d $r2d (8) > > Into: > 1: add f64 $r0d $r0d 0.500000 (8) > > This has been tested with the 2 double shader tests which I just send to > the piglet list. On a gk208 (gk110 / SM35) card, and by checking the output > of nouveau_compiler with both nvdisasm and envydis on gf100 / gk104 / gm107. > > Regards, > > Hans

...ripathi B.Tech. Part-III Electronics Engineering IIT-BHU (Varanasi) On Wed, Jan 18, 2017 at 3:48 AM, Karol Herbst <karolherbst at gmail.com> wrote: > Hi, > > I think a nice project would be to write an application to figure out > those latencies automatically maybe even based on envydis. > > It could generate latency information based on thread count, register > usage, instruction/instruction class, hw unit used. Or even tries to figure > out what kind of units exist. Like instructions out of a group which are > free to issue/execute after instructions out of anoth...

Hello, I am quite interested in the project "Instruction Scheduler" under X.org. Please tell me where can I find a detailed idea of the project and how to start it. I think I have the given prerequisites. Regards Shailesh Tripathi Shailesh Tripathi B.Tech. Part-IV Electronics Engineering IIT-BHU (Varanasi) -------------- next part -------------- An HTML attachment was scrubbed... URL:

https://bugs.freedesktop.org/show_bug.cgi?id=72939 Priority: medium Bug ID: 72939 Assignee: nouveau at lists.freedesktop.org Summary: [nv96] Freespace 2 open crashes Severity: normal Classification: Unclassified OS: All Reporter: madman2003 at gmail.com Hardware: Other Status: NEW

helps two alien isolation shaders shader-db: total instructions in shared programs : 4251497 -> 4251494 (-0.00%) total gprs used in shared programs : 513962 -> 513962 (0.00%) total local used in shared programs : 29797 -> 29797 (0.00%) total bytes used in shared programs : 38960264 -> 38960232 (-0.00%) local gpr inst bytes helped

MAD IMM has a very specific SDST == SSRC2 requirement, so don't emit Signed-off-by: Roy Spliet <rspliet at eclipso.eu> --- .../drivers/nouveau/codegen/nv50_ir_emit_nv50.cpp | 18 ++++++++++++------ .../drivers/nouveau/codegen/nv50_ir_target_nv50.cpp | 2 +- 2 files changed, 13 insertions(+), 7 deletions(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_nv50.cpp

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Untested beyond compiling a few shaders to see if they look like they might work. nvdisasm agrees with envydis's decoding of these things. Will definitely get ahold of a G200 to run tests on before pushing this. .../drivers/nouveau/codegen/nv50_ir_emit_nv50.cpp | 94 ++++++++++++++++++--- .../nouveau/codegen/nv50_ir_lowering_nv50.cpp | 97 +++++++++++++++++++++- .../nouveau/codegen/nv50_ir_tar...

https://bugs.freedesktop.org/show_bug.cgi?id=78161 Priority: medium Bug ID: 78161 Assignee: nouveau at lists.freedesktop.org Summary: [NV96] Artifacts in output of fragment program containing not unrolled loops with conditional break Severity: normal Classification: Unclassified OS: Linux (All)