[Nouveau] Access to add a r300_reg database to rules-ng?
phillipezolt at gmail.com
Wed Jun 27 11:25:58 PDT 2007
> And a note about kmmio trace: I expect a redesign of the binary log
> format in the next weeks. The binary dumps are easier to handle
> automatically and the current format is just broken. Once the new
> format is in place, we can write new cool tools, and most
> importantly, share binary dumps without problems ;-)
In your redesign of the binary dump format, could you add the ability
to store multiple PCs per sample? (ie, so that I can do backtraces (4
frames deep?) ) rather than just a single PC?
About 3-4 months ago, I hacked some code for kmmio which would walk
the stack and record the pc X frames above the current register
access. Since I didn't figure out how to record multiple PCs per
sample, I hardcoded how far up the stack I would walk, and did
multiple runs (while changing the frame by recompiling) to get 3
(run 1 => current PC )
(run 2 => one frame up)
(run 3 => two frames up)
I would then combine the runs by hand, and turn the addresses into
frames by using '/proc/kallsyms'. It was very useful info, but
Since fglrx actually has useful symbols in the kernel module, I was
able to determine the meaning of some of the register accesses by
looking at the stack trace. (It wasn't enough to just look at the PC,
since it was in some generic 'do_mmio' function... I needed the frame
above it.) I would like to do this again for some of the other
registers that I don't know the meaning of yet..
This might be useful for nvidia as well.
BTW. I can send you the patch if you want, but it is very i386
specific & (if I remember) it requires framepointers.
> Pekka "PQ" Paalanen
More information about the Nouveau