/openbmc/linux/drivers/gpu/drm/i915/gt/ |
H A D | intel_reset.c | 38 static void client_mark_guilty(struct i915_gem_context *ctx, bool banned) in client_mark_guilty() argument 48 if (banned) in client_mark_guilty() 69 bool banned; in mark_guilty() local 85 /* Cool contexts are too cool to be banned! (Used for reset testing.) */ in mark_guilty() 87 banned = false; in mark_guilty() 102 banned = !i915_gem_context_is_recoverable(ctx); in mark_guilty() 104 banned = true; in mark_guilty() 105 if (banned) in mark_guilty() 106 drm_dbg(&ctx->i915->drm, "context %s: guilty %d, banned\n", in mark_guilty() 109 client_mark_guilty(ctx, banned); in mark_guilty() [all …]
|
H A D | gen8_engine_cs.c | 467 * request is banned. Before the request is started, it is assumed in gen8_emit_init_breadcrumb()
|
H A D | intel_execlists_submission.c | 443 * requests' payloads for any banned requests. But first, we must in reset_active()
|
/openbmc/bmcweb/ |
H A D | DEVELOPING.md | 40 …[Banned functions](https://github.com/intel/safestringlib/wiki/SDL-List-of-Banned-Functions "Banne…
|
/openbmc/pldm/pldmtool/oem/ibm/ |
H A D | oem_ibm_state_set.hpp | 76 "Banned Platform Fail"},
|
/openbmc/linux/drivers/gpu/drm/i915/ |
H A D | i915_file_private.h | 95 * is reached, client is considered banned and submitting more work
|
H A D | i915_request.h | 137 * is banned and those active requests need to be cancelled.
|
H A D | i915_request.c | 253 * is-banned?, or we know the request is already inflight. in i915_request_active_engine()
|
/openbmc/linux/drivers/gpu/drm/i915/pxp/ |
H A D | intel_pxp.c | 42 * content are banned. Any further attempt at using them in an execbuf call is 487 * The context has been banned, no need to keep the wakeref. in intel_pxp_invalidate()
|
/openbmc/phosphor-dbus-interfaces/yaml/com/google/gbmc/ |
H A D | Hoth.interface.yaml | 9 like LoadTokens are banned. This method should be called from the IPMI
|
/openbmc/linux/drivers/gpu/drm/i915/gem/ |
H A D | i915_gem_context_types.h | 386 #define CONTEXT_FAST_HANG_JIFFIES (120 * HZ) /* 3 hangs within 120s? Banned! */
|
H A D | i915_gem_userptr.c | 479 * object, in that several ioctls are banned. These are the CPU access
|
H A D | i915_gem_context.c | 1328 * as banned, any incomplete request, including any running, will in __cancel_engine() 1335 * kill the banned context, we fallback to doing a local reset in __cancel_engine() 2283 "client %s[%d] banned from creating ctx\n", in i915_gem_context_create_ioctl()
|
H A D | i915_gem_execbuffer.c | 912 * this context, because the context itself will be banned when in eb_lookup_vma()
|
/openbmc/libcper/ |
H A D | json-schema.c | 381 //If additional properties are banned, validate that no additional properties exist. in validate_object()
|
/openbmc/linux/drivers/gpu/drm/i915/gt/uc/ |
H A D | intel_guc_submission.c | 695 * request resubmitted after the context was banned. in __guc_add_request() 1067 bool pending_disable, pending_enable, deregister, destroyed, banned; in scrub_guc_desc_for_outstanding_g2h() local 1099 banned = context_banned(ce); in scrub_guc_desc_for_outstanding_g2h() 1120 if (banned) { in scrub_guc_desc_for_outstanding_g2h() 3122 * timeout to the minimum value (1 us) so the banned context in guc_context_revoke() 4755 bool banned; in intel_guc_sched_done_process_msg() local 4774 banned = context_banned(ce); in intel_guc_sched_done_process_msg() 4781 if (banned) { in intel_guc_sched_done_process_msg() 4845 guc_dbg(guc, "Got context reset notification: 0x%04X on %s, exiting = %s, banned = %s\n", in guc_handle_context_reset()
|
/openbmc/linux/arch/powerpc/kernel/ |
H A D | eeh.c | 1486 * during reset, which should be banned as it's always in eeh_pe_reset()
|
/openbmc/linux/include/uapi/drm/ |
H A D | i915_drm.h | 2017 * the context is forever banned instead.
|
/openbmc/linux/tools/include/uapi/drm/ |
H A D | i915_drm.h | 2017 * the context is forever banned instead.
|
/openbmc/linux/drivers/gpu/drm/ci/ |
H A D | testlist.txt | 21 gem_eio@banned
|
/openbmc/linux/drivers/mtd/nand/raw/ |
H A D | nand_base.c | 5654 * as been banned for the benefit of the ->init_ecc()/cleanup_ecc() hooks.
|