On Tue, May 13, 2014 at 4:57 PM, Marek Olšák <mar...@gmail.com> wrote: > Hi Rob, > > Roland is right. > > The function which resets the query result is begin_query.
ahh, ok.. it seemed from piglit tests that *something* (other than destroy) should be resetting the query, but I wasn't quite sure what. I'll fix my wording (and query implementation ;-)) BR, -R > Marek > > On Tue, May 13, 2014 at 4:21 AM, Rob Clark <robdcl...@gmail.com> wrote: >> From: Rob Clark <robcl...@freedesktop.org> >> >> It wasn't completely clear from the docs, so I had to figure out by >> looking at piglit results. Hopefully this saves the next driver writer >> implementing queries some time. >> >> Signed-off-by: Rob Clark <robcl...@freedesktop.org> >> --- >> src/gallium/docs/source/context.rst | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/src/gallium/docs/source/context.rst >> b/src/gallium/docs/source/context.rst >> index fc8dd16..9278796 100644 >> --- a/src/gallium/docs/source/context.rst >> +++ b/src/gallium/docs/source/context.rst >> @@ -307,6 +307,10 @@ returned). Otherwise, if the ``wait`` parameter is >> FALSE, the call >> will not block and the return value will be TRUE if the query has >> completed or FALSE otherwise. >> >> +``get_query_result`` (if it returns TRUE) will clear/reset previous query >> +results. In other words, subsequent calls to ``get_query_result`` will >> +only return results since the previous call. >> + >> The interface currently includes the following types of queries: >> >> ``PIPE_QUERY_OCCLUSION_COUNTER`` counts the number of fragments which >> -- >> 1.9.0 >> >> _______________________________________________ >> mesa-dev mailing list >> mesa-dev@lists.freedesktop.org >> http://lists.freedesktop.org/mailman/listinfo/mesa-dev _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
