From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 6/9] drm/i915: Disable waitboosting for fence_wait()
Date: Fri, 15 Jul 2016 15:07:57 +0300 [thread overview]
Message-ID: <1468584477.4896.6.camel@linux.intel.com> (raw)
In-Reply-To: <20160715114943.GO1841@nuc-i3427.alporthouse.com>
On pe, 2016-07-15 at 12:49 +0100, Chris Wilson wrote:
> On Fri, Jul 15, 2016 at 12:08:05PM +0100, Chris Wilson wrote:
> >
> > On Fri, Jul 15, 2016 at 01:47:34PM +0300, Joonas Lahtinen wrote:
> > >
> > > On pe, 2016-07-15 at 11:11 +0100, Chris Wilson wrote:
> > > >
> > > > +#define NO_WAITBOOST ERR_PTR(-1)
> > > This does not seem to be a very common idiom in kernel, just add flags
> > > maybe.
> > I find the special values for the client (including the existing NULL
> > client) much more informative.
> Is it more pleasant with...?
>
> diff --git a/drivers/gpu/drm/i915/i915_gem_request.c b/drivers/gpu/drm/i915/i915_gem_request.c
> index bfec4a88707d..aedc15d46463 100644
> --- a/drivers/gpu/drm/i915/i915_gem_request.c
> +++ b/drivers/gpu/drm/i915/i915_gem_request.c
> @@ -713,7 +713,7 @@ complete:
> *timeout = 0;
> }
>
> - if (!IS_ERR_OR_NULL(rps) &&
> + if (IS_RPS_CLIENT(rps) &&
> req->fence.seqno == req->engine->last_submitted_seqno) {
> /* The GPU is now idle and this client has stalled.
> * Since no other client has submitted a request in the
> diff --git a/drivers/gpu/drm/i915/i915_gem_request.h b/drivers/gpu/drm/i915/i915_gem_request.h
> index f7f497a07893..b3fe80d4eb63 100644
> --- a/drivers/gpu/drm/i915/i915_gem_request.h
> +++ b/drivers/gpu/drm/i915/i915_gem_request.h
> @@ -207,6 +207,7 @@ void __i915_add_request(struct drm_i915_gem_request *req,
>
> struct intel_rps_client;
I almost suggested #define RPS_CLIENT(n) ERR_PTR(-n), but this is
somewhat better already.
> #define NO_WAITBOOST ERR_PTR(-1)
> +#define IS_RPS_CLIENT(p) (!IS_ERR_OR_NULL(p))
>
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-07-15 12:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 10:11 Derive requests from dma-buf fence Chris Wilson
2016-07-15 10:11 ` [PATCH 1/9] drm/i915: Flush logical context image out to memory upon suspend Chris Wilson
2016-07-15 10:41 ` Mika Kuoppala
2016-07-15 11:11 ` Chris Wilson
2016-07-15 10:11 ` [PATCH 2/9] drm/i915: Move GEM request routines to i915_gem_request.c Chris Wilson
2016-07-15 10:41 ` Joonas Lahtinen
2016-07-15 10:43 ` Mika Kuoppala
2016-07-15 10:11 ` [PATCH 3/9] drm/i915: Retire oldest completed request before allocating next Chris Wilson
2016-07-15 10:11 ` [PATCH 4/9] drm/i915: Mark all current requests as complete before resetting them Chris Wilson
2016-07-15 10:11 ` [PATCH 5/9] drm/i915: Derive GEM requests from dma-fence Chris Wilson
2016-07-15 10:11 ` [PATCH 6/9] drm/i915: Disable waitboosting for fence_wait() Chris Wilson
2016-07-15 10:47 ` Joonas Lahtinen
2016-07-15 11:08 ` Chris Wilson
2016-07-15 11:49 ` Chris Wilson
2016-07-15 12:07 ` Joonas Lahtinen [this message]
2016-07-15 10:49 ` Mika Kuoppala
2016-07-15 11:06 ` Chris Wilson
2016-07-15 11:53 ` [PATCH v2] " Chris Wilson
2016-07-15 12:25 ` Mika Kuoppala
2016-07-15 10:11 ` [PATCH 7/9] drm/i915: Disable waitboosting for mmioflips/semaphores Chris Wilson
2016-07-15 11:08 ` Mika Kuoppala
2016-07-15 12:50 ` Chris Wilson
2016-07-15 12:26 ` Mika Kuoppala
2016-07-15 10:11 ` [PATCH 8/9] drm/i915: Wait on external rendering for GEM objects Chris Wilson
2016-07-18 10:18 ` Chris Wilson
2016-07-19 6:45 ` Daniel Vetter
2016-07-15 10:11 ` [PATCH 9/9] drm/i915: Mark imported dma-buf objects as being coherent Chris Wilson
2016-07-15 11:33 ` Mika Kuoppala
2016-07-15 10:48 ` ✗ Ro.CI.BAT: failure for series starting with [1/9] drm/i915: Flush logical context image out to memory upon suspend 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=1468584477.4896.6.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/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