On Fri, Jun 17, 2016 at 08:09:02AM +0100, Arun Siluvery wrote: > This change extends the idea of reset_counter variable to engine reset by > creating additional variables for each engine. Least significant bit is set > to mark the engine reset is pending and once reset is successful it is > incremented again, this is further used to count the no of engine resets. You still haven't split it up into the seperate fields. atomic_t flags; atomic_t global_reset_counter; atomic_t engine_reset_counter[NUM_ENGINES]; That way checking whether a reset in progress is just one atomic read, not N+1. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
