After a couple of kernel recompiles I got oprofile to work, and it was reporting that most of its time was spend in default_idle for both glxgears and qw-client-glx (from QuakeForge CVS).
After speaking to one of the oprofile ppl, they seem to think that this is as much as I will get cause it appears that the amount of time spent in default_idle could be pointing to the driver waiting for IRQ's. Does DRI enable busmastering for PCI (if busmastering works that way) and does DRI make the card utilize it for PCI. With the speeds even AGPx1 gets I'm assuming the same questions for AGP would be answered with a yes, which is why I'm asking exclusively for PCI. How can I check to see if the driver is using busmastering for my card? Here is the top few lines from the glxgears output. samples % image name app name symbol name 135746 45.8645 vmlinux vmlinux default_idle 23597 7.9727 r200_dri.so glxgears emit_vec12 7932 2.6800 vmlinux vmlinux mark_offset_tsc 6826 2.3063 oprofiled oprofiled sfile_match 5062 1.7103 libc-2.3.2.so glxgears (no symbols) 5016 1.6948 vmlinux vmlinux mask_and_ack_8259A 4726 1.5968 vmlinux glxgears __copy_from_user_ll 4505 1.5221 radeon glxgears radeon_cp_cmdbuf 3326 1.1238 r200_dri.so glxgears r200_emit_state_list ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
