All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Shrink search list for active timelines
Date: Wed, 16 May 2018 07:32:45 +0100	[thread overview]
Message-ID: <152645236598.1362.18215699934089877345@mail.alporthouse.com> (raw)
In-Reply-To: <20180515143149.4795-1-chris@chris-wilson.co.uk>

Quoting Chris Wilson (2018-05-15 15:31:49)
> When switching to the kernel context, we force the switch to occur after
> all currently active requests (so that we know the GPU won't switch
> immediately away and the kernel context remains current as we work). To
> do so we have to inspect all the timelines and add a fence from the
> active work to queue our switch afterwards. We can use the tracked set
> of active rings to shrink our search for active timelines.
> 
> v2: Use a local to shrink the list_for_each_entry()
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

And pushed, thanks kindly for the review.
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2018-05-16  6:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-13 13:46 [PATCH] drm/i915: Shrink search list for active timelines Chris Wilson
2018-05-13 14:20 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-05-13 15:07 ` ✓ Fi.CI.IGT: " Patchwork
2018-05-15 13:42 ` [PATCH] " Tvrtko Ursulin
2018-05-15 13:48   ` Chris Wilson
2018-05-15 14:31 ` [PATCH v2] " Chris Wilson
2018-05-16  6:32   ` Chris Wilson [this message]
2018-05-15 15:16 ` ✓ Fi.CI.BAT: success for drm/i915: Shrink search list for active timelines (rev2) Patchwork
2018-05-16  1:23 ` ✓ 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=152645236598.1362.18215699934089877345@mail.alporthouse.com \
    --to=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 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.