TL;DR:  VGL_READBACK=sync is always required for VP 9, 10 and 11.

On 06/09/14 05:21 PM, DRC wrote:
> Can you clarify your statement about requesting PBOs in Viewperf? So
> are you saying that, with v8.1 through v10, VP will fail with VGL but
> not by default? I.e. it will only fail if PBOs are requested in
> Viewperf? (saying "only works" is ambiguous-- I don't know whether
> you meant that VGL only works in that situation or that the offending
> code is only activated in that situation.) The reason I ask is that I
> know I've used VP 9 with VGL successfully, and I'm pretty sure it was
> since PBO readback became the default in VGL.

Urgh, this is getting messy. So I went back and did an actual `vglrun 
<viewperf>` run[1] for all versions rather than just comparing the 
viewperf.c code to VP 10 which I'd initially debugged on.

1.  VP 8.1 actually does *not* have any problem on non-Windows boxes. 
(It has near-identical code to VP9/10 with regard to glGenBuffers, 
except I'd missed that an '#endif // WIN32' had moved a few lines.)

2. Viewperf 9.0(.3) and 10.0 SEGV with default viewperf build/settings 
because glGenBuffers is not initialized.

3. Viewperf 11 also SEGVs, but not because glGenBuffers isn't 
initialized; rather it dies somewhere within NVIDIA's glBindBuffer().

4. The part you were asking about: Viewperf 9 and 10 have  -vbo / -va / 
| -ea options to initialize the static glGenBuffers function pointer 
(and others). One must manually edit the makefile to enable these, but 
if enabled they only serve to produce the same SEGV as in 3.

I'd like to eventually understand why the SEGV in 3 occurs (presumably 
bad buffer interaction between VGL and VP), but this isn't high on my 
list since a) VGL_READBACK=sync works, and b) I'm quite used by now, to 
saying "ViewPerf is a GPU benchmark, it doesn't make much sense to run 
it in any kind of remote setting."

-Nathan


[1] Using Fedora Core 18 box with VGL 2.3.3.

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
VirtualGL-Devel mailing list
VirtualGL-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-devel

Reply via email to