Hi Chris, Thanks for quick response. I see that these tests from HANG section. Probably all tests with unclear behavior are put here. But what is about the test gem_exec_bad_domains? It also contains BAD_GTT_DEST with the same value. This test isn't from HANG section. Pavel -----Original Message----- From: Chris Wilson [mailto:chris@xxxxxxxxxxxxxxxxxx] Sent: Friday, May 15, 2015 5:17 PM To: Popov, Pavel E Cc: intel-gfx@xxxxxxxxxxxxxxxxxxxxx Subject: Re: [PATCH] tests/gem_bad_address: Adapt test to ppgtt to pass with command parser On Fri, May 15, 2015 at 04:05:01PM +0600, Pavel Popov wrote: > The gem_bad_address test started to fail on Gen7 with enabled command parser. > Error message is printed because MI_GLOBAL_GTT equals to MI_MEM_VIRTUAL: > "CMD: Rejected command 0x10600002 for bitmask 0x00400000...". > MI_MEM_VIRTUAL means global gtt. This bit shouldn't be set for ppgtt. > > Changed test like it was done previously for storedw tests in the commit: > afbdc7af8d9324ae065c47d6122bb020c579fd0a. Heh, gem_bad_address is supposed to fail ;-) As with gem_bad_blit, this is testing antiquated notions of what is allowed: BAD_GTT_DEST is not what it claims to be. -Chris -- Chris Wilson, Intel Open Source Technology Centre _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
