path: root/Events/XDC2014/XDC2014PitoisetNouveau.mdwn
diff options
authormperes <mperes@web>2014-10-10 05:54:40 -0700
committerxorg <>2014-10-10 05:54:40 -0700
commit8560da1a8e7b09248b088c1f07f42e76ff83222a (patch)
tree4b14b70bce3f5e5eed7814dcc5a4bb63b6316058 /Events/XDC2014/XDC2014PitoisetNouveau.mdwn
parent3b7ab6e3eab0eea758ee91fdb9d0de58dbdb90fd (diff)
Diffstat (limited to 'Events/XDC2014/XDC2014PitoisetNouveau.mdwn')
1 files changed, 2 insertions, 0 deletions
diff --git a/Events/XDC2014/XDC2014PitoisetNouveau.mdwn b/Events/XDC2014/XDC2014PitoisetNouveau.mdwn
index eeec4d82..ddcee4d1 100644
--- a/Events/XDC2014/XDC2014PitoisetNouveau.mdwn
+++ b/Events/XDC2014/XDC2014PitoisetNouveau.mdwn
@@ -1,3 +1,5 @@
# 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).