From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Alex Goins <agoins@nvidia.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH i915 v4 1/2] i915: wait for fences in mmio_flip()
Date: Fri, 20 Nov 2015 13:30:38 +0200 [thread overview]
Message-ID: <20151120113038.GG4437@intel.com> (raw)
In-Reply-To: <38886598294448ffc3b77374c917d74e5b1536d6.1447796827.git.agoins@nvidia.com>
On Thu, Nov 19, 2015 at 07:51:25PM -0800, Alex Goins wrote:
> If a buffer is backed by dmabuf, wait on its reservation object's fences
> before flipping.
>
> Signed-off-by: Alex Goins <agoins@nvidia.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 14 ++++++++++++++
> 1 file changed, 14 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index b2270d5..4867ff0 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -44,6 +44,8 @@
> #include <drm/drm_plane_helper.h>
> #include <drm/drm_rect.h>
> #include <linux/dma_remapping.h>
> +#include <linux/reservation.h>
> +#include <linux/dma-buf.h>
>
> /* Primary plane formats for gen <= 3 */
> static const uint32_t i8xx_primary_formats[] = {
> @@ -11088,6 +11090,8 @@ static bool use_mmio_flip(struct intel_engine_cs *ring,
> return true;
> else if (i915.enable_execlists)
> return true;
> + else if (obj->base.dma_buf && obj->base.dma_buf->resv->fence_excl)
> + return true;
> else
> return ring != i915_gem_request_get_ring(obj->last_write_req);
> }
> @@ -11170,8 +11174,18 @@ static void ilk_do_mmio_flip(struct intel_crtc *intel_crtc)
> static void intel_do_mmio_flip(struct intel_crtc *intel_crtc)
> {
> struct drm_device *dev = intel_crtc->base.dev;
> + struct intel_framebuffer *intel_fb =
> + to_intel_framebuffer(intel_crtc->base.primary->fb);
> + struct drm_i915_gem_object *obj = intel_fb->obj;
> u32 start_vbl_count;
>
> + /* For framebuffer backed by dmabuf, wait for fence */
> + if (obj->base.dma_buf) {
> + reservation_object_wait_timeout_rcu(
> + obj->base.dma_buf->resv,
> + false, true, MAX_SCHEDULE_TIMEOUT);
> + }
> +
Why is this in do_mmio_flip() rather than next to the normal seqno wait
at the previous level?
> intel_mark_page_flip_active(intel_crtc);
>
> intel_pipe_update_start(intel_crtc, &start_vbl_count);
> --
> 1.9.1
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-11-20 11:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 3:51 [PATCH i915 v4 0/2] PRIME Synchronization Alex Goins
2015-11-20 3:51 ` [PATCH i915 v4 1/2] i915: wait for fences in mmio_flip() Alex Goins
2015-11-20 8:21 ` Daniel Vetter
2015-11-20 21:51 ` Alexander Goins
2015-11-20 11:30 ` Ville Syrjälä [this message]
2015-11-20 21:51 ` Alexander Goins
2015-11-20 3:51 ` [PATCH i915 v4 2/2] i915: wait for fence in prepare_plane_fb Alex Goins
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=20151120113038.GG4437@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=agoins@nvidia.com \
--cc=dri-devel@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