<div dir="auto"><div><br><div class="gmail_extra"><br><div class="gmail_quote">On Feb 7, 2017 12:54 PM, "Emil Velikov" <<a href="mailto:emil.l.velikov@gmail.com">emil.l.velikov@gmail.com</a>> wrote:<br type="attribution"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="quoted-text">On 7 February 2017 at 11:23, Jan Ziak <<a href="mailto:0xe2.0x9a.0x9b@gmail.com">0xe2.0x9a.0x9b@gmail.com</a>> wrote:<br>
> On Mon, Feb 6, 2017 at 11:48 PM, Marek Olšák <<a href="mailto:maraeo@gmail.com">maraeo@gmail.com</a>> wrote:<br>
>> On Mon, Feb 6, 2017 at 9:27 PM, Jan Ziak <<a href="mailto:0xe2.0x9a.0x9b@gmail.com">0xe2.0x9a.0x9b@gmail.com</a>> wrote:<br>
>>> Hello<br>
>>><br>
>>> I am against application profiles - in the form of "a<br>
>>> community-maintained whitelist of apps" or in any other form<br>
>>> explicitly associating the name/ID of an app with a Mesa variable<br>
>>> which controls the behavior of Mesa.<br>
>>><br>
>>> Application profiles would be a manifestation of poor algorithms in<br>
>>> the OpenGL implementation.<br>
>><br>
>> No, it's called incremental progress.<br>
>><br>
>> The Mesa community doesn't have resources to develop a multithreaded<br>
>> solution that is perfect from day 1. Incremental progress will get us<br>
>> there eventually. Or not. But it's the only way to get somewhere with<br>
>> our limited resources.<br>
>><br>
>> Marek<br>
><br>
> No. The point is: You are proposing a transient solution that isn't<br>
> automated (i.e: a solution that isn't resembling machine learning in<br>
> any way). <a href="https://en.wikipedia.org/wiki/Machine_learning" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/<wbr>Machine_learning</a><br>
><br>
</div>Have to agree with Marek here. An explicit opt-in solution would be<br>
nice to start with considering our resources.<br>
<div class="quoted-text"><br>
> Instead, why don't you introduce a simple C/C++ variable controlling<br>
> whether to use glthread?<br>
</div>...<br>
<div class="quoted-text">> The above solution would be totally simple to implement in Mesa. A<br>
> human-maintained whitelist is clearly a subpar solution due to<br>
> multiple factors.<br>
><br>
</div>Ideally we'll have something like this as we get to the point where no<br>
crashes or rendering issues are present.<br>
Until then this is not an option - it will deteriorate the user<br>
experience very significantly.<br>
<br>
Marek, please send the series to the list and _if_ you want guard the<br>
lot behind a configure switch.<br>
Alternatively a big warning message [when the variable is toggled]<br>
might be nice idea ?<br></blockquote></div></div></div><div dir="auto"><br></div><div dir="auto">A configure switch isn't necessary. It's guarded by the drirc toggle mesa_glthread, which is also an environment variable. The warning is printed by the XML config code just like for any other driconf/drirc toggle.</div><div dir="auto"><br></div><div dir="auto">Marek</div><div dir="auto"><br></div><div dir="auto"><br></div><div dir="auto"><div class="gmail_extra"><div class="gmail_quote"><blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks<br>
<font color="#888888">Emil<br>
</font></blockquote></div><br></div></div></div>