On 03/01/2015 11:06 PM, Ilia Mirkin wrote:
On Sun, Mar 1, 2015 at 4:55 PM, Samuel Pitoiset
wrote:
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 per
On Sun, Mar 1, 2015 at 4:55 PM, Samuel Pitoiset
wrote:
>
> 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 doe
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
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
wrote:
> Signed-off-by: Samuel Pitoiset
>
Signed-off-by: Samuel Pitoiset
---
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.
See the driver code for other, lesser
