From: jeff.mcgee@intel.com
To: intel-gfx@lists.freedesktop.org
Cc: ben@bwidawsk.net, kalyan.kondapally@intel.com
Subject: [RFC 0/8] Force preemption
Date: Fri, 16 Mar 2018 11:30:57 -0700 [thread overview]
Message-ID: <20180316183105.16027-1-jeff.mcgee@intel.com> (raw)
From: Jeff McGee <jeff.mcgee@intel.com>
Force preemption uses engine reset to enforce a limit on the time
that a request targeted for preemption can block. This feature is
a requirement in automotive systems where the GPU may be shared by
clients of critically high priority and clients of low priority that
may not have been curated to be preemption friendly. There may be
more general applications of this feature. I'm sharing as an RFC to
stimulate that discussion and also to get any technical feedback
that I can before submitting to the product kernel that needs this.
I have developed the patches for ease of rebase, given that this is
for the moment considered a non-upstreamable feature. It would be
possible to refactor hangcheck to fully incorporate force preemption
as another tier of patience (or impatience) with the running request.
Jeff McGee (8):
drm/i915: Downgrade tasklet GEM_BUG_ON for request not completed
drm/i915: Skip CSB processing on invalid CSB tail
drm/i915: Execlists to mark the HWSP upon preemption finished
drm/i915: Add a wait_for routine with more exact timeout
drm/i915: Consider preemption when finding the active request
drm/i915: Repair the preemption context if hit by reset
drm/i915: Allow reset without error capture
drm/i915: Force preemption to complete via engine reset
drivers/gpu/drm/i915/i915_drv.c | 14 +++++-
drivers/gpu/drm/i915/i915_drv.h | 4 ++
drivers/gpu/drm/i915/i915_gem.c | 86 ++++++++++++++++++++++++++++++---
drivers/gpu/drm/i915/i915_irq.c | 75 ++++++++++++++++------------
drivers/gpu/drm/i915/i915_params.c | 3 ++
drivers/gpu/drm/i915/i915_params.h | 1 +
drivers/gpu/drm/i915/intel_drv.h | 22 +++++++++
drivers/gpu/drm/i915/intel_engine_cs.c | 53 ++++++++++++++++++++
drivers/gpu/drm/i915/intel_lrc.c | 81 +++++++++++++++++++++++++++++--
drivers/gpu/drm/i915/intel_ringbuffer.h | 20 +++++++-
10 files changed, 314 insertions(+), 45 deletions(-)
--
2.16.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-03-16 18:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 18:30 jeff.mcgee [this message]
2018-03-16 18:30 ` [RFC 1/8] drm/i915: Downgrade tasklet GEM_BUG_ON for request not completed jeff.mcgee
2018-03-16 20:30 ` Chris Wilson
2018-03-16 18:30 ` [RFC 2/8] drm/i915: Skip CSB processing on invalid CSB tail jeff.mcgee
2018-03-16 20:30 ` Chris Wilson
2018-03-16 18:31 ` [RFC 3/8] drm/i915: Execlists to mark the HWSP upon preemption finished jeff.mcgee
2018-03-16 18:31 ` [RFC 4/8] drm/i915: Add a wait_for routine with more exact timeout jeff.mcgee
2018-03-16 18:31 ` [RFC 5/8] drm/i915: Consider preemption when finding the active request jeff.mcgee
2018-03-16 18:31 ` [RFC 6/8] drm/i915: Repair the preemption context if hit by reset jeff.mcgee
2018-03-16 18:31 ` [RFC 7/8] drm/i915: Allow reset without error capture jeff.mcgee
2018-03-16 20:33 ` Chris Wilson
2018-03-16 18:31 ` [RFC 8/8] drm/i915: Force preemption to complete via engine reset jeff.mcgee
2018-03-16 20:39 ` Chris Wilson
2018-03-16 20:44 ` Chris Wilson
2018-03-16 18:59 ` ✗ Fi.CI.BAT: failure for Force preemption Patchwork
2018-03-16 20:53 ` [RFC 0/8] " Chris Wilson
2018-03-16 21:03 ` Chris Wilson
2018-03-16 23:04 ` [PATCH] force-preempt-reset Chris Wilson
2018-03-16 23:45 ` ✗ Fi.CI.BAT: failure for force-preempt-reset Patchwork
2018-03-16 22:34 ` [RFC 0/8] Force preemption Chris Wilson
2018-03-21 17:26 jeff.mcgee
2018-03-22 9:22 ` Tvrtko Ursulin
2018-03-22 9:28 ` Chris Wilson
2018-03-22 14:34 ` Jeff McGee
2018-03-22 15:35 ` Chris Wilson
2018-03-22 15:44 ` Jeff McGee
2018-03-22 15:57 ` Tvrtko Ursulin
2018-03-22 16:01 ` Jeff McGee
2018-03-22 17:41 ` Tvrtko Ursulin
2018-03-22 19:08 ` Jeff McGee
2018-03-22 19:59 ` Bloomfield, Jon
2018-03-23 13:20 ` Joonas Lahtinen
2018-03-23 13:37 ` Chris Wilson
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=20180316183105.16027-1-jeff.mcgee@intel.com \
--to=jeff.mcgee@intel.com \
--cc=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kalyan.kondapally@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.