On Wed, Dec 07, 2016 at 01:58:17PM +0000, Chris Wilson wrote: > More changes to GEM are on the cards, so before touching it again, let's > try and nail down how the internals are meant to work. The advantage > of mock testing is that we can write a universal test independent of the > hw (e.g. testing physical object creation) and we can inspect internal > state which should be able to spot subtle bugs easier than mashing the > uabi. The downside to mock testing is that it doubles the upfront cost > of every patch submission (if you change internal state, you're likely > going to upset a test) and adds maintainance burden tracking change to > external API (on the other hand it catches those silent changes that > would lead to broken code). I should also say it does not alleviate the need for uabi behaviour testing as well. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
