> + /* Start in a signaled state so that even non-submitted batches > + * (those that have no draw/clear) can be waited upon. > + */
When would this happen? Presumably if a batch does nothing whatsoever, it doesn't make sense to wait on it. > #include "pan_resource.h" > > + /* Batch that created this fence object. Will become NULL at batch > + * submission time. This field is mainly here to know whether the > + * batch has been flushed or not. > + */ > + struct panfrost_batch *batch; Could this be replaced by just a `bool flushed`, or do we actually use the value in a later patch? _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
