All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: "Bloomfield, Jon" <jon.bloomfield@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 5/5] drm/i915: Cancel non-persistent contexts on close
Date: Tue, 06 Aug 2019 15:41:28 +0100	[thread overview]
Message-ID: <156510248816.2892.16071640056614739337@skylake-alporthouse-com> (raw)
In-Reply-To: <AD48BB7FB99B174FBCC69E228F58B3B68B3A9B4F@fmsmsx120.amr.corp.intel.com>

Quoting Bloomfield, Jon (2019-08-06 15:26:07)
> > -----Original Message-----
> > From: Chris Wilson <chris@chris-wilson.co.uk>
> > +
> > +     /*
> > +      * If the user has disabled hangchecking, we can not be sure that
> > +      * the batches will ever complete and let the context be freed.
> > +      * Forcibly kill off any remaining requests in this case.
> > +      */
> 
> Persistence is independent of hangcheck which makes the above comment unrepresentative of the below code.
> Do we even need a comment here, it looks self-explanatory? Instead maybe comment the defaulting state in __createContext() to make the connection between hangcheck and persistence?

Indeed, it can be moved almost verbatim to explain the default behaviour
and expand upon the cgroup wish. (Rather than using hangcheck modparam,
let the sysadmin specify defaults for groups of processes -- planning
for when we remove hangcheck entirely.)
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-08-06 14:42 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06 13:47 [PATCH 1/5] drm/i915: Only enqueue already completed requests Chris Wilson
2019-08-06 13:47 ` [PATCH 2/5] drm/i915/execlists: Force preemption Chris Wilson
2019-08-06 13:47 ` [PATCH 3/5] drm/i915: Mark up "sentinel" requests Chris Wilson
2019-08-06 14:29   ` Mika Kuoppala
2019-08-06 14:47     ` Chris Wilson
2019-08-06 13:47 ` [PATCH 4/5] drm/i915/execlists: Cancel banned contexts on schedule-out Chris Wilson
2019-08-06 13:47 ` [PATCH 5/5] drm/i915: Cancel non-persistent contexts on close Chris Wilson
2019-08-06 14:11   ` Chris Wilson
2019-08-06 14:26   ` Bloomfield, Jon
2019-08-06 14:41     ` Chris Wilson [this message]
2019-08-07 13:22   ` Chris Wilson
2019-08-07 14:04     ` Bloomfield, Jon
2019-08-07 14:14       ` Chris Wilson
2019-08-07 14:33         ` Bloomfield, Jon
2019-08-07 15:08           ` Chris Wilson
2019-08-07 15:29             ` Bloomfield, Jon
2019-08-07 15:38               ` Chris Wilson
2019-08-07 16:51               ` Chris Wilson
2019-08-07 17:12                 ` Bloomfield, Jon
2019-08-09 23:34   ` Chris Wilson
2019-08-12 14:39     ` Bloomfield, Jon
2019-08-12 14:51       ` Chris Wilson
2019-08-06 14:25 ` [PATCH 1/5] drm/i915: Only enqueue already completed requests Mika Kuoppala
2019-08-06 14:44   ` Chris Wilson
2019-08-06 14:51 ` ✗ Fi.CI.BAT: failure for series starting with [1/5] " 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=156510248816.2892.16071640056614739337@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jon.bloomfield@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.