Quoting Rodrigo Vivi (2018-02-26 20:53:07) > Now that we are spreading the places we can manipulate > sagv status let's protect it. This needs a lot more information about the protection you need. "sagv status" is too similar to sagv_status, so it seems like you are simply talking about protecting access to that variable, which doesn't make sense. So I presume you are talking about ordering enable/disable, which opens up a heap of questions as to why, and what should be done about the implied races in wanting to disable sagv before/during/immediately-after enabling it. (Even accepting the race conditions exist, you only needed to correct access to sagv; a mutex for a single variable is massive overkill. So again, the reader is left presuming you intend more.) -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
