On 01/11/2016 11:10 AM, John Harrison wrote:
> On 08/01/2016 22:46, Chris Wilson wrote:
>> On Fri, Jan 08, 2016 at 06:47:26PM +, john.c.harri...@intel.com wrote:
>>> +void i915_gem_request_notify(struct intel_engine_cs *ring, bool
>>> fence_locked)
>>> +{
>>> +struct drm_i915_gem_request *
On 08/01/2016 22:46, Chris Wilson wrote:
On Fri, Jan 08, 2016 at 06:47:26PM +, john.c.harri...@intel.com wrote:
+void i915_gem_request_notify(struct intel_engine_cs *ring, bool fence_locked)
+{
+ struct drm_i915_gem_request *req, *req_next;
+ unsigned long flags;
u32 seqn
On Fri, Jan 08, 2016 at 10:14:16PM +, Chris Wilson wrote:
> On Fri, Jan 08, 2016 at 06:47:26PM +, john.c.harri...@intel.com wrote:
> > From: John Harrison
> >
> > The intended usage model for struct fence is that the signalled status
> > should be set on demand rather than polled. That is
On Fri, Jan 08, 2016 at 06:47:26PM +, john.c.harri...@intel.com wrote:
> +void i915_gem_request_notify(struct intel_engine_cs *ring, bool fence_locked)
> +{
> + struct drm_i915_gem_request *req, *req_next;
> + unsigned long flags;
> u32 seqno;
>
> - seqno = req->ring->get_se
On Fri, Jan 08, 2016 at 06:47:26PM +, john.c.harri...@intel.com wrote:
> From: John Harrison
>
> The intended usage model for struct fence is that the signalled status
> should be set on demand rather than polled. That is, there should not
> be a need for a 'signaled' function to be called ev
From: John Harrison
The intended usage model for struct fence is that the signalled status
should be set on demand rather than polled. That is, there should not
be a need for a 'signaled' function to be called everytime the status
is queried. Instead, 'something' should be done to enable a signal
