All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Improve anti-pre-emption w/a for compute workloads (rev7)
Date: Thu, 29 Sep 2022 02:33:10 -0000	[thread overview]
Message-ID: <166441879072.11951.10730813118711178771@emeril.freedesktop.org> (raw)
In-Reply-To: <20220929021813.2172701-1-John.C.Harrison@Intel.com>

== Series Details ==

Series: Improve anti-pre-emption w/a for compute workloads (rev7)
URL   : https://patchwork.freedesktop.org/series/100428/
State : warning

== Summary ==

Error: dim checkpatch failed
502f12c04cdf drm/i915/guc: Limit scheduling properties to avoid overflow
-:44: CHECK:MACRO_ARG_REUSE: Macro argument reuse 'field' - possible side-effects?
#44: FILE: drivers/gpu/drm/i915/gt/intel_engine_cs.c:516:
+#define CLAMP_PROP(field) \
+	do { \
+		u64 clamp = intel_clamp_##field(engine, engine->props.field); \
+		if (clamp != engine->props.field) { \
+			drm_notice(&engine->i915->drm, \
+				   "Warning, clamping %s to %lld to prevent overflow\n", \
+				   #field, clamp); \
+			engine->props.field = clamp; \
+		} \
+	} while (0)

total: 0 errors, 0 warnings, 1 checks, 223 lines checked
29c47abff7df drm/i915: Fix compute pre-emption w/a to apply to compute engines
911b8d3394fd drm/i915: Make the heartbeat play nice with long pre-emption timeouts
3924354f431a drm/i915: Improve long running compute w/a for GuC submission



  parent reply	other threads:[~2022-09-29  2:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29  2:18 [PATCH v4 0/4] Improve anti-pre-emption w/a for compute workloads John.C.Harrison
2022-09-29  2:18 ` [Intel-gfx] " John.C.Harrison
2022-09-29  2:18 ` [PATCH v4 1/4] drm/i915/guc: Limit scheduling properties to avoid overflow John.C.Harrison
2022-09-29  2:18   ` [Intel-gfx] " John.C.Harrison
2022-09-29  7:39   ` Tvrtko Ursulin
2022-09-29  2:18 ` [PATCH v4 2/4] drm/i915: Fix compute pre-emption w/a to apply to compute engines John.C.Harrison
2022-09-29  2:18   ` [Intel-gfx] " John.C.Harrison
2022-09-29  2:18 ` [PATCH v4 3/4] drm/i915: Make the heartbeat play nice with long pre-emption timeouts John.C.Harrison
2022-09-29  2:18   ` [Intel-gfx] " John.C.Harrison
2022-09-29  7:42   ` Tvrtko Ursulin
2022-09-29 16:21     ` John Harrison
2022-09-30  9:22       ` Tvrtko Ursulin
2022-09-30 17:44         ` John Harrison
2022-10-03  7:53           ` Tvrtko Ursulin
2022-10-03 12:00             ` Tvrtko Ursulin
2022-10-05 18:48               ` John Harrison
2022-10-06 10:03                 ` Tvrtko Ursulin
2022-09-29  2:18 ` [PATCH v4 4/4] drm/i915: Improve long running compute w/a for GuC submission John.C.Harrison
2022-09-29  2:18   ` [Intel-gfx] " John.C.Harrison
2022-09-29  7:44   ` Tvrtko Ursulin
2022-09-29  2:33 ` Patchwork [this message]
2022-09-29  2:33 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Improve anti-pre-emption w/a for compute workloads (rev7) Patchwork
2022-09-29  2:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-30  2:28 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=166441879072.11951.10730813118711178771@emeril.freedesktop.org \
    --to=patchwork@emeril.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.