|
|
Created:
6 years, 7 months ago by epenner Modified:
6 years, 7 months ago CC:
chromium-reviews, piman+watch_chromium.org Base URL:
https://chromium.googlesource.com/chromium/src.git@master Visibility:
Public. |
DescriptionGPU: Use virtual contexts on NVidia.
They asked for this since optimizing MakeCurrent will take
significantly longer.
BUG=369316
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=268029
Patch Set 1 #Patch Set 2 : Change version. #Patch Set 3 : Use second work-around #Patch Set 4 : Use command-line-flag. #Patch Set 5 : Use work-around flag, not command-line #Patch Set 6 : Whitespace. #Messages
Total messages: 23 (0 generated)
Ptal. Daniel, is there any way to toggle virtual contexts via a command-line such that they can play with this after the fact?
On 2014/05/01 22:27:30, epenner wrote: > Ptal. > > Daniel, is there any way to toggle virtual contexts via a command-line such that > they can play with this after the fact? LGTM You can use --disable-gpu-driver-bug-workarounds to disable all of them.
The CQ bit was checked by epenner@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/epenner@chromium.org/269593008/1
The CQ bit was unchecked by zmo@chromium.org
Please always update the list version. (I unchecked the CQ, please update then check CQ again)
On 2014/05/01 23:31:47, Zhenyao Mo wrote: > Please always update the list version. > > (I unchecked the CQ, please update then check CQ again) Thanks for the heads up!
The CQ bit was checked by epenner@chromium.org
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/epenner@chromium.org/269593008/20001
The CQ bit was unchecked by sievers@chromium.org
On second thought: Can we check GL_VERSION beginswith OpenGL ES 3.1? Just so that we don't accidentally trigger something unexpected on older devices. I know there is no good reason why it shouldn't work, but you know how it goes :)
On 2014/05/02 00:01:03, sievers wrote: > On second thought: Can we check GL_VERSION beginswith OpenGL ES 3.1? > > Just so that we don't accidentally trigger something unexpected on older > devices. > I know there is no good reason why it shouldn't work, but you know how it goes > :) Yeah especially if we want to merge. Ideally though these could be merged for 36. Or maybe we can just remove this second one if it gets better. Anyway, ptal for two separate workarounds.
On 2014/05/02 01:10:09, epenner wrote: > On 2014/05/02 00:01:03, sievers wrote: > > On second thought: Can we check GL_VERSION beginswith OpenGL ES 3.1? > > > > Just so that we don't accidentally trigger something unexpected on older > > devices. > > I know there is no good reason why it shouldn't work, but you know how it goes > > :) > > Yeah especially if we want to merge. Ideally though these could be merged for > 36. Or maybe we can just remove this second one if it gets better. > > Anyway, ptal for two separate workarounds. Actually this doesn't work yet. It looks like the GL_VERSION actually starts with "OpenGL ES 3.1", and for some reason that's still not triggering. I'll look into it.
Okay. We chatted and I've put together this version for merge. I had to move the Android specific code such that it sets the command-line early enough to detect it and apply the workaround. But it doesn't look like that should cause any problems. Btw, I'll get rid of this entire bit of Android code and move it to where we set Android compositor flags, in a follow up.
Actually, this avoids touching the command-line, by adding the work-around to the set directly instead. Ptal.
LGTM as far as it's tested.
On 2014/05/03 00:42:23, Zhenyao Mo wrote: > LGTM as far as it's tested. Thanks. I've tested on the device we are interested in to make sure it works. Also, sorry I've got to run and can't do the proper fix to support this in JSON. Alternatively, we could just enable virtual contexts for all NV devices for 36, since we'll have longer to test them.
The CQ bit was checked by epenner@google.com
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/epenner@chromium.org/269593008/100001
The CQ bit was unchecked by epenner@google.com
The CQ bit was checked by epenner@google.com
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/epenner@chromium.org/269593008/120001
Message was sent while issue was closed.
Change committed as 268029 |