From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Cc: Ben Widawsky <ben@bwidawsk.net>,
Ben Widawsky <benjamin.widawsky@intel.com>
Subject: Re: [PATCH 1/3] drm/i915: i915_gem_object_sync must handle NULL
Date: Wed, 11 Apr 2012 19:41:04 +0100 [thread overview]
Message-ID: <1334169670_371200@CP5-2952> (raw)
In-Reply-To: <1334168301-4699-1-git-send-email-ben@bwidawsk.net>
On Wed, 11 Apr 2012 11:18:19 -0700, Ben Widawsky <ben@bwidawsk.net> wrote:
> When I extracted the synchronization code for implementing semaphorified
> pageflips (74f5f6e0), I neglected the non pipelined case which also
> calls this code. The modesetting code wants to make sure the object has
> finished rendering to the frame before configuring the scanout (ie.
> non-pipelined case).
>
> As a result of a follow on discussion on IRC, I've decided to add a
> comment about the function itself which received much inspiration from
> Chris as well. So really, this patch was ghost-written by Chris :).
>
> Reported-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Ben Widawsky <benjamin.widawsky@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Tested-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-04-11 18:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 18:18 [PATCH 1/3] drm/i915: i915_gem_object_sync must handle NULL Ben Widawsky
2012-04-11 18:18 ` [PATCH 2/3] drm/i915: fix for when semaphore updates fail Ben Widawsky
2012-04-11 18:42 ` Chris Wilson
2012-04-11 18:18 ` [PATCH 3/3] drm/i915: hide (seqno-1) in ringbuffer code Ben Widawsky
2012-04-11 18:43 ` Chris Wilson
2012-04-11 18:41 ` Chris Wilson [this message]
2012-04-11 19:01 ` [PATCH 1/3] drm/i915: i915_gem_object_sync must handle NULL Daniel Vetter
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=1334169670_371200@CP5-2952 \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--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.