path: root/Events/XDC2014/XDC2014PitoisetNouveau.mdwn
diff options
authormperes <mperes@web>2014-10-05 18:48:11 -0700
committerxorg <>2014-10-05 18:48:11 -0700
commit3972e00a8909ff58674cb21928c54934ffed8838 (patch)
tree48a4b6947d2602ff48fd359dfbf8387bf01e2ea8 /Events/XDC2014/XDC2014PitoisetNouveau.mdwn
parentd38b580e343073e0b0a4b2def42fd7c61cc54780 (diff)
Diffstat (limited to 'Events/XDC2014/XDC2014PitoisetNouveau.mdwn')
1 files changed, 3 insertions, 0 deletions
diff --git a/Events/XDC2014/XDC2014PitoisetNouveau.mdwn b/Events/XDC2014/XDC2014PitoisetNouveau.mdwn
new file mode 100644
index 00000000..eeec4d82
--- /dev/null
+++ b/Events/XDC2014/XDC2014PitoisetNouveau.mdwn
@@ -0,0 +1,3 @@
+# Samuel Pitoiset - Nouveau: Expose NVIDIA's performance counters to the userspace for nv50/Tesla
+A hardware performance counter is a set of special registers which are used to store the counts of hardware-related activities. Hardware counters are often used by developers to identify performance bottlenecks in their applications. There are two types of counters offered by NVIDIA which provide data directly from various points of the GPU. Compute counters are used for OpenCL, while graphics counters give detailed information for OpenGL/Direct3D. It took me two Google Summer of Code (GSoC) to manage to expose them in Nouveau. In this presentation, I will first sum up my GSoC 2013 where I reverse engineered and implemented compute counters for nvc0/fermi in mesa. Then, I will introduce my GSOC2014's work to design a kernel interface to expose compute- and graphics-related counters to the userspace (mesa).