search for: jwrdegoede

...n to not >> work, >> I guess I can give it a try. > > Compute support is not supported on GK110+, yeah... > > If you provide me a MMT trace of, for example, vectorAdd from the CUDA samples I could have a look. Ok, here is a MMT trace of vectorAdd: https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz Regards, Hans

...Easily verified by sticking > PUSH_KICK's everywhere. I do not believe that that is the problem, in my case it clearly seems to be a pitch / swizzle problem rather then a synchronizarion problem, here is what my desktop with gnome shell looks like when using DRI2: https://fedorapeople.org/~jwrdegoede/nv46-gnome-shell-good.jpg And this is what it looks like when using DRI3: https://fedorapeople.org/~jwrdegoede/nv46-gnome-shell-bad.jpg The DRI2 screenshot is made with Mario's 2 patches on top of current master: http://lists.freedesktop.org/archives/nouveau/2015-July/021740.html http://lis...

...? > > > Sorry I only included a small bit of the program in my original mail > because I found the use of "MOV" instructions to load constants > suspicious, is that normal ? > > I've put a log with NV50_PROG_DEBUG=1 output here: > > https://fedorapeople.org/~jwrdegoede/nbody.log > > nvdisasm -b SM30 for the generated binary code is here: > > https://fedorapeople.org/~jwrdegoede/nbody.disasm > > There are already .tgsi, .hex and .bin files there if > you find those easier to use then the > NV50_PROG_DEBUG=1 output. > > >> >&g...

...mpute >> code to work. The code from mesa/src/gallium/tests/trivial.c >> works. >> >> So now I'm trying to get a "native" tgsi kernel to run via >> clover, I'm using Francisco's nbody.c example for this: >> >> https://fedorapeople.org/~jwrdegoede/nbody.c >> >> Which does not work, at first I thought there was an issue >> with the setup of the input / output buffers, but that seems to >> work fine, and moreover I finally got the smart idea to look >> in dmesg, which says: >> >> [ 9920.802435] nouveau...

...it just goes off executing into the ether? Sorry I only included a small bit of the program in my original mail because I found the use of "MOV" instructions to load constants suspicious, is that normal ? I've put a log with NV50_PROG_DEBUG=1 output here: https://fedorapeople.org/~jwrdegoede/nbody.log nvdisasm -b SM30 for the generated binary code is here: https://fedorapeople.org/~jwrdegoede/nbody.disasm There are already .tgsi, .hex and .bin files there if you find those easier to use then the NV50_PROG_DEBUG=1 output. > > On Tue, Dec 15, 2015 at 12:00 PM, Ilia Mirkin <...

...only included a small bit of the program in my original mail >> because I found the use of "MOV" instructions to load constants >> suspicious, is that normal ? >> >> I've put a log with NV50_PROG_DEBUG=1 output here: >> >> https://fedorapeople.org/~jwrdegoede/nbody.log >> >> nvdisasm -b SM30 for the generated binary code is here: >> >> https://fedorapeople.org/~jwrdegoede/nbody.disasm >> >> There are already .tgsi, .hex and .bin files there if >> you find those easier to use then the >> NV50_PROG_DEBUG=1 o...

...>> >> I do not believe that that is the problem, in my case it clearly >> seems to be a pitch / swizzle problem rather then a synchronizarion >> problem, here is what my desktop with gnome shell looks like when >> using DRI2: >> >> https://fedorapeople.org/~jwrdegoede/nv46-gnome-shell-good.jpg >> >> And this is what it looks like when using DRI3: >> >> https://fedorapeople.org/~jwrdegoede/nv46-gnome-shell-bad.jpg >> >> The DRI2 screenshot is made with Mario's 2 patches on top of >> current master: >> >> h...

...n on top of llvm trunk, and added a commit on top to actual get it build with the latest trunk. So currently I'm at the point where I've just taken Francisco's code, and made it compile, no more and no less. I have a git repo with this work available here: http://cgit.freedesktop.org/~jwrdegoede/llvm/ So the next step would be to test this and see if it actually does anything, questions: 1) Does anyone have a simple test case / command where I can invoke just llvm and get TGSI asm output to check ? 2) Assuming I get the above to (somewhat) work, is there a way to make llvm show the outp...

...only included a small bit of the program in my original mail >> because I found the use of "MOV" instructions to load constants >> suspicious, is that normal ? >> >> I've put a log with NV50_PROG_DEBUG=1 output here: >> >> https://fedorapeople.org/~jwrdegoede/nbody.log >> >> nvdisasm -b SM30 for the generated binary code is here: >> >> https://fedorapeople.org/~jwrdegoede/nbody.disasm >> >> There are already .tgsi, .hex and .bin files there if >> you find those easier to use then the >> NV50_PROG_DEBUG=1 o...

Hi, After a few distractions I'm back to work on the llvm tgsi backend. I've added clang integration and I can now compile a simple opencl program to something which sort of looks like tgsi. You can find my latest work on this here: http://cgit.freedesktop.org/~jwrdegoede/llvm http://cgit.freedesktop.org/~jwrdegoede/clang (the latter may still need to sync) I've a little test program of which I have 3 versions now, 1 raw gallium calls + a tgsi kernel 2 opencl calls to clover + a tgsi kernel 3 opencl calls to clover + an opencl kernel 1 and 2 have been tested o...

...try. >> >> >> Compute support is not supported on GK110+, yeah... >> >> If you provide me a MMT trace of, for example, vectorAdd from the CUDA >> samples I could have a look. > > > Ok, here is a MMT trace of vectorAdd: > > https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz You don't have permission to access /~jwrdegoede/vectorAdd.log.gz on this server. Unfortunately valgrind creates files with og-rwx, and the various tools like gzip and scp maintain those permissions. So you have to manually fix it. -ilia

...king about commit rights, I guess it would be >> convenient for all if I would get commit rights myself? I promise I won't >> push anythings without acks. > > Yes sure, I trust you, no worries. :-) > >> >> I already have a freedesktop.org account, my username is jwrdegoede. > > Please open a ticket on bugs.freedesktop to ask for commit rights. Done: https://bugs.freedesktop.org/show_bug.cgi?id=94594 Can you or Ilia please ack this ? Thanks, Hans

On 01-12-15, Samuel Pitoiset wrote: >>> Ok, here is a MMT trace of vectorAdd: >>> >>> https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz >> >> Hi Hans, >> >> Thanks a lot. > > Well, I didn't know but Martin has a GK208... > I just tested the compute support on his card and ... it works without > any changes. :-) > > I'm sorry, I was sure the compute support...

https://bugs.freedesktop.org/show_bug.cgi?id=91992 Bug ID: 91992 Summary: [NV4C] computer hangs after few minutes of use Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau

...As part of my compute work I'm trying to get some TGSI compute code to work. The code from mesa/src/gallium/tests/trivial.c works. So now I'm trying to get a "native" tgsi kernel to run via clover, I'm using Francisco's nbody.c example for this: https://fedorapeople.org/~jwrdegoede/nbody.c Which does not work, at first I thought there was an issue with the setup of the input / output buffers, but that seems to work fine, and moreover I finally got the smart idea to look in dmesg, which says: [ 9920.802435] nouveau 0000:01:00.0: gr: TRAP ch 6 [007f7fa000 nbody[31881]] [ 9920...

...mplers, textures and so on) yourself. This is a bit painful but should work as expected. > >> >> As you know I'm working on a llvm tgsi backend, >> it actually produces some output now, if you want >> to take a peek it lives here: >> http://cgit.freedesktop.org/~jwrdegoede/llvm > > I'm currently building your TGSI branch. :-) Cool, note this is very very preliminary. This really is just curro's work ported to the latest llvm trunk without me having added anything (yet). >> Before working further on this I want to take >> a bottom up approa...

Hi Maarten, xf86-video-nouveau causes a garbled display when running gnome-shell on nv4x (tested with nv43 and nv46) since this commit: http://cgit.freedesktop.org/nouveau/xf86-video-nouveau/commit/?id=241e7289f25a342a457952b9b0e539c2f0b81d99 I've seen some discussion about issues caused by enabling dri, but AFAIK no solution let. I have time to help with debugging / fixing this, but I

https://bugs.freedesktop.org/show_bug.cgi?id=90871 Bug ID: 90871 Summary: NV30: Xfwm4 use_compositing - garbled display Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: critical Priority: medium Component: Driver/nouveau Assignee:

...distractions I'm back to work on the llvm tgsi backend. I've >> added clang integration and I can now compile a simple opencl program >> to something which sort of looks like tgsi. >> >> You can find my latest work on this here: >> http://cgit.freedesktop.org/~jwrdegoede/llvm >> http://cgit.freedesktop.org/~jwrdegoede/clang >> (the latter may still need to sync) >> >> I've a little test program of which I have 3 versions now, >> 1 raw gallium calls + a tgsi kernel >> 2 opencl calls to clover + a tgsi kernel >> 3 opencl...

...because at some point NVIDIA didn't use it > by default anywhere. You're right I needed to specify NVreg_EnableMSI=1, with that set /proc/interrupts shows that MSI is used. Here is an of running glxgears with the binary driver using msi interrupts mmiotrace: https://fedorapeople.org/~jwrdegoede/nvidia-bin-nv46-msi-on-glxgears.mmiotrace.gz AFAIK there are some nouveau tools to parse this a bit, right ? I'm going to call it a day for today, if you can give me some pointers what to do with the mmiotrace to find a potential fix for the msi issues, that would be appreciated. BTW I had t...