[07:36] <mlankhorst> "Hello, world!\n"
[11:25] <mlankhorst> does pre-sandy bridge even allow snooped access?
[11:36] <mlankhorst> woops wrong channel :)
[13:16] <mlankhorst> .. running kernel with kmemcheck is scary
[22:11] <mlankhorst> RAOF: great success :D
[22:11] <mlankhorst> dmabufmgr seems to work
[22:12] <mlankhorst> i adapted the code for nouveau to use the hardware for waiting
[22:21] <mlankhorst> which turned into a 800 line patch :s
[22:54] <RAOF> Huge success!
[22:57] <mlankhorst> RAOF: yeah was just tracking 2 bugs today, first one was in my test program with how I marked intel relocations. I needed a noop for testing, but it ended up executing the address as command, second one was probably due to some stuff not firing in idle stait, and workaround was adding some busyloops
[22:58] <mlankhorst> eg schedtool ... 'while true; do true; done' on all cpus
[22:59] <RAOF> :)
[23:01] <mlankhorst> http://people.canonical.com/~mlankhorst/prime-sync/ full patchset, probably best to use drm-intel-next-queue git tree
[23:02] <mlankhorst> i wanted to grab the delayed fput git tree too, but it hangs early on in boot
[23:04] <jwi> a hacky max_cstate=0? ;)
[23:05] <RAOF> I may have to get you to give me some pointers for what needs to be done on the radeon side. That might be a fun project at 2am when Zoë's crying :)
[23:07] <mlankhorst> RAOF: oh I could do it easily myself
[23:08] <mlankhorst> RAOF: anyhow you need to create a read-only mapping and add a wait-ge op for a dma-buf
[23:09] <mlankhorst> well, either read-only or userspace inaccessible..
[23:10] <mlankhorst> ive glanced through the documentation so I know r600 supports the operations at least
[23:12] <mlankhorst> but the easiest case is adapting i915
[23:13] <mlankhorst> oh btw, DON'T create a gem object for your sync bo, it will deadlock
[23:14] <mlankhorst> besides that radeon uses ttm so there's no real  need for involving gem
[23:28] <mlankhorst> RAOF: night 
[23:28] <RAOF> Good night :)(