41  *   them need to keeep the workaround programming: the approach taken in the
65  *   this is just a special case of a MMIO workaround (as we write the list of
71  * - Workaround batchbuffers: buffers that get executed automatically by the
74  *   programming sequences when switching contexts. The support for workaround
79  *      is reached in the context restore. Workaround batchbuffer in the driver
159 			drm_err(&i915->drm, "No space for workaround init!\n");  in _wa_add()
364 	 * workaround for a possible hang in the unlikely event a TLB  in gen8_ctx_workarounds_init()
492 	 * is a workaround for a possible hang in the unlikely event  in gen9_ctx_workarounds_init()
644 	 * This is not the same workaround as in early Gen9 platforms, where  in icl_ctx_workarounds_init()
721 	 * workaround.  in gen12_ctx_workarounds_init()
829 	 * This is a "fake" workaround defined by software to ensure we  in fakewa_disable_nestedbb_mode()
844 	 * behavior for userspace, so we'll apply a fake workaround to set it  in fakewa_disable_nestedbb_mode()
876  * gen12_ctx_gt_fake_wa_init() aren't programmingan official workaround
878  * Adding those context register programming in context workaround
902 	 * Fake workarounds are not the actual workaround but  in __intel_engine_init_ctx_wa()
903 	 * programming of context registers using workaround framework.  in __intel_engine_init_ctx_wa()
1051 	/* Apply the WaDisableRHWOOptimizationForRenderHang:ivb workaround. */  in ivb_gt_workarounds_init()
1447 	 * This is not a documented workaround, but rather an optimization  in icl_gt_workarounds_init()
1456  * only be provided on the GT workaround list rather than
1457  * the engine-specific workaround list.
1490 	 * preventing i915 from modifying it for this workaround.  Skip the  in gen12_gt_workarounds_init()
1491 	 * readback verification for this workaround on debug builds; if the  in gen12_gt_workarounds_init()
1492 	 * workaround doesn't stick due to firmware behavior, it's not an error  in gen12_gt_workarounds_init()
1703  * workaround infrastructure to make sure they're (re)applied at the proper
1805 		       "%s workaround lost on %s! (reg[%x]=0x%x, relevant bits were 0x%x vs expected 0x%x)\n",  in wa_verify()
2147 		/* Required by recommended tuning setting (not a workaround) */  in tgl_whitelist_build()
2162 		/* Required by recommended tuning setting (not a workaround) */  in dg2_whitelist_build()
2201 		/* Required by recommended tuning setting (not a workaround) */  in xelpg_whitelist_build()
2276  * which are not part of an official workaround defined by the
2278  * Adding programming of those register inside workaround will
2816  * workaround infrastructure to ensure that they're automatically added to
2854  * workaround list (whichever engine has the XXXX flag).
2993 	 * to a single RCS/CCS engine's workaround list since  in engine_init_workarounds()