44  *   them need to keeep the workaround programming: the approach taken in the
69  *   this is just a special case of a MMIO workaround (as we write the list of
75  * - Workaround batchbuffers: buffers that get executed automatically by the
78  *   programming sequences when switching contexts. The support for workaround
83  *      is reached in the context restore. Workaround batchbuffer in the driver
162 			drm_err(&i915->drm, "No space for workaround init!\n");  in _wa_add()
361 	 * workaround for a possible hang in the unlikely event a TLB  in gen8_ctx_workarounds_init()
489 	 * is a workaround for a possible hang in the unlikely event  in gen9_ctx_workarounds_init()
641 	 * This is not the same workaround as in early Gen9 platforms, where  in icl_ctx_workarounds_init()
718 	 * workaround.  in gen12_ctx_workarounds_init()
834 	 * This is a "fake" workaround defined by software to ensure we  in fakewa_disable_nestedbb_mode()
849 	 * behavior for userspace, so we'll apply a fake workaround to set it  in fakewa_disable_nestedbb_mode()
881  * gen12_ctx_gt_fake_wa_init() aren't programmingan official workaround
883  * Adding those context register programming in context workaround
907 	 * Fake workarounds are not the actual workaround but  in __intel_engine_init_ctx_wa()
908 	 * programming of context registers using workaround framework.  in __intel_engine_init_ctx_wa()
1066 	/* Apply the WaDisableRHWOOptimizationForRenderHang:ivb workaround. */  in ivb_gt_workarounds_init()
1446 	 * This is not a documented workaround, but rather an optimization  in icl_gt_workarounds_init()
1455  * only be provided on the GT workaround list rather than
1456  * the engine-specific workaround list.
1489 	 * preventing i915 from modifying it for this workaround.  Skip the  in gen12_gt_workarounds_init()
1490 	 * readback verification for this workaround on debug builds; if the  in gen12_gt_workarounds_init()
1491 	 * workaround doesn't stick due to firmware behavior, it's not an error  in gen12_gt_workarounds_init()
1623  * workaround infrastructure to make sure they're (re)applied at the proper
1715 		       "%s workaround lost on %s! (reg[%x]=0x%x, relevant bits were 0x%x vs expected 0x%x)\n",  in wa_verify()
2057 		/* Required by recommended tuning setting (not a workaround) */  in tgl_whitelist_build()
2072 		/* Required by recommended tuning setting (not a workaround) */  in dg2_whitelist_build()
2087 		/* Required by recommended tuning setting (not a workaround) */  in xelpg_whitelist_build()
2158  * which are not part of an official workaround defined by the
2160  * Adding programming of those register inside workaround will
2689 	/* boilerplate for any CCS engine workaround */  in ccs_engine_wa_init()
2695  * workaround infrastructure to ensure that they're automatically added to
2735 	 * Wa_14019159160: This workaround, along with others, leads to  in ccs_engine_wa_mode()
2757  * workaround list (whichever engine has the XXXX flag).
2879 	 * to a single RCS/CCS engine's workaround list since  in engine_init_workarounds()