Why wouldn't they always just be enabled :) Also, do you have to set it to get MP counters on kepler+? And why is it called "compute" if it enables performance counters... probably does more than that, no?
On Sun, Mar 1, 2015 at 6:44 AM, Samuel Pitoiset <samuel.pitoi...@gmail.com> wrote: > Signed-off-by: Samuel Pitoiset <samuel.pitoi...@gmail.com> > --- > docs/envvars.html | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/docs/envvars.html b/docs/envvars.html > index 31d14a4..cb3eba0 100644 > --- a/docs/envvars.html > +++ b/docs/envvars.html > @@ -227,6 +227,10 @@ for details. > <li>See the driver code for other, lesser-used variables. > </ul> > > +<h3>Nouveau driver environment variables</h3> > +<ul> > +<li>NVC0_COMPUTE - enable MP performance counters for nvc0+ > +</ul> > > <p> > Other Gallium drivers have their own environment variables. These may change > -- > 2.3.0 > > _______________________________________________ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
