From: John Harrison <john.c.harrison@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
<Intel-GFX@Lists.FreeDesktop.Org>
Cc: DRI-Devel@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/guc: Limit scheduling properties to avoid overflow
Date: Thu, 24 Feb 2022 11:51:07 -0800 [thread overview]
Message-ID: <77a7da0d-4cea-00c5-0073-44c9779b14a5@intel.com> (raw)
In-Reply-To: <c1472196-260a-d2c8-c508-10fe58d4cd47@intel.com>
On 2/24/2022 11:19, John Harrison wrote:
> [snip]
>
> I'll change it to _uses_ and repost, then.
>
[ 7.683149] kernel BUG at drivers/gpu/drm/i915/gt/uc/intel_guc.h:367!
Told you that one went bang.
John.
next prev parent reply other threads:[~2022-02-24 19:51 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 21:33 [Intel-gfx] [PATCH 0/3] Improve anti-pre-emption w/a for compute workloads John.C.Harrison
2022-02-18 21:33 ` [Intel-gfx] [PATCH 1/3] drm/i915/guc: Limit scheduling properties to avoid overflow John.C.Harrison
2022-02-22 9:52 ` Tvrtko Ursulin
2022-02-22 10:39 ` Tvrtko Ursulin
2022-02-23 2:11 ` John Harrison
2022-02-23 12:13 ` Tvrtko Ursulin
2022-02-23 19:03 ` John Harrison
2022-02-24 9:59 ` Tvrtko Ursulin
2022-02-24 19:19 ` John Harrison
2022-02-24 19:51 ` John Harrison [this message]
2022-02-25 17:44 ` Tvrtko Ursulin
2022-02-25 17:06 ` Tvrtko Ursulin
2022-02-25 17:39 ` John Harrison
2022-02-28 16:11 ` Tvrtko Ursulin
2022-02-28 18:32 ` John Harrison
2022-03-01 10:50 ` Tvrtko Ursulin
2022-03-01 19:57 ` John Harrison
2022-03-02 9:20 ` Tvrtko Ursulin
2022-03-02 18:07 ` John Harrison
2022-02-23 0:52 ` Ceraolo Spurio, Daniele
2022-02-23 2:15 ` John Harrison
2022-02-18 21:33 ` [Intel-gfx] [PATCH 2/3] drm/i915/gt: Make the heartbeat play nice with long pre-emption timeouts John.C.Harrison
2022-02-22 11:19 ` Tvrtko Ursulin
2022-02-23 2:45 ` John Harrison
2022-02-23 13:58 ` Tvrtko Ursulin
2022-02-23 20:00 ` John Harrison
2022-02-24 11:41 ` Tvrtko Ursulin
2022-02-24 19:45 ` John Harrison
2022-02-25 18:14 ` Tvrtko Ursulin
2022-02-25 18:48 ` John Harrison
2022-02-28 17:12 ` Tvrtko Ursulin
2022-02-28 18:55 ` John Harrison
2022-03-01 12:09 ` Tvrtko Ursulin
2022-03-01 20:59 ` John Harrison
2022-03-02 11:07 ` Tvrtko Ursulin
2022-03-02 17:55 ` John Harrison
2022-03-03 9:55 ` Tvrtko Ursulin
2022-03-03 19:09 ` John Harrison
2022-03-04 12:36 ` Tvrtko Ursulin
2022-02-18 21:33 ` [Intel-gfx] [PATCH 3/3] drm/i915: Improve long running OCL w/a for GuC submission John.C.Harrison
2022-02-19 2:54 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for Improve anti-pre-emption w/a for compute workloads Patchwork
2022-02-19 3:33 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-02-22 9:53 ` [Intel-gfx] [PATCH 0/3] " Tvrtko Ursulin
2022-02-23 2:22 ` John Harrison
2022-02-23 12:00 ` Tvrtko Ursulin
2022-02-24 20:02 ` John Harrison
2022-02-25 16:36 ` Tvrtko Ursulin
2022-02-25 17:11 ` John Harrison
2022-02-25 17:39 ` Tvrtko Ursulin
2022-02-25 18:01 ` John Harrison
2022-02-25 18:29 ` Tvrtko Ursulin
2022-02-25 19:03 ` John Harrison
2022-02-28 15:32 ` Tvrtko Ursulin
2022-02-28 19:17 ` John Harrison
2022-03-02 11:21 ` Tvrtko Ursulin
2022-03-02 17:40 ` John Harrison
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=77a7da0d-4cea-00c5-0073-44c9779b14a5@intel.com \
--to=john.c.harrison@intel.com \
--cc=DRI-Devel@Lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox