[Mesa-dev] [PATCH] docs: describe the NVC0_COMPUTE envvar

[Samuel Pitoiset]

On 03/01/2015 07:21 PM, Ilia Mirkin wrote:
> 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?

It is not enabled by default because compute support on Fermi has weird 
effects on 3D. And, I didn't find the time to investigate about this, 
that's why it is still a bit experimental. :)

Actually, NVC0_COMPUTE allows compute support which is required for MP 
counters in order to polls them. However, we only have to set it for 
nvc0:nve4 chipsets, so the documentation of this envvar could be more 
accurate.

Should I have to submit a v2 and improve the documentation by something 
like "NVC0_COMPUTE - enable compute support which is required for MP 
performance counters on nvc0:nve4" ?

>
> On Sun, Mar 1, 2015 at 6:44 AM, Samuel Pitoiset
> <samuel.pitoiset at gmail.com> wrote:
>> Signed-off-by: Samuel Pitoiset <samuel.pitoiset at 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 at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/mesa-dev