From: Daniel Vetter <daniel@ffwll.ch>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: Intel-gfx@lists.freedesktop.org
Subject: Re: [RFC v3] drm/i915: Android native sync support
Date: Wed, 28 Jan 2015 10:25:22 +0100 [thread overview]
Message-ID: <20150128092522.GL4764@phenom.ffwll.local> (raw)
In-Reply-To: <54C795E6.6020004@linux.intel.com>
On Tue, Jan 27, 2015 at 01:43:02PM +0000, Tvrtko Ursulin wrote:
>
> On 01/27/2015 12:18 PM, Chris Wilson wrote:
> >On Tue, Jan 27, 2015 at 12:13:14PM +0000, Tvrtko Ursulin wrote:
> >>On 01/27/2015 11:40 AM, Chris Wilson wrote:
>
> [snip]
>
> >>>Explain how fence_release interacts with enable_signalling. Presumably
> >>>either the core fence routines cleanup the outstanding signalling, or we
> >>>are expected to. Doing so will remove the requirement for the extra
> >>>ref/unref (including the worker).
> >>
> >>I think normally we would be expected to use fence_get/put on the
> >>signaling side of things but that is not possible here since struct
> >>fence is embedded in the request.
> >>
> >>So as it is, sync_fence_release will tear everything down with our
> >>callback still on the irq_queue which is what taking a request
> >>reference sorts out.
> >
> >So you are saying that we have a callback for when the fence is
> >discarded by userspace and we ignore that opportunity for disabling
> >interrupt generation, and remove the extra request references?
>
> I can change it to work like that sure, don't see anything obvious
> preventing this rework. Can use the fence lock to avoid wait queue removal
> race and that should be pretty much it.
>
> On a related not, do you have any ideas for submitting a batch which can
> either keep the GPU busy for a configurable time, or until signaled by
> something else (possibly another batch). Gen agnostic ideally? :)
self-tuning busy loads using the blitter/rendercopy. We have bazillion of
existing copypasta in igt tests for this, would be great if someone
extracts it into a real igt helper library and converts everyone over.
Iirc the one in kms_flip or gem_wait is probably the best starting point.
There's no way afaik to block a batch on an mbox or similar from
userspace.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-01-28 9:24 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-22 11:15 [RFC] drm/i915: Android native sync support Tvrtko Ursulin
2015-01-22 11:42 ` Chris Wilson
2015-01-22 13:41 ` Tvrtko Ursulin
2015-01-22 13:49 ` Chris Wilson
2015-01-22 13:56 ` Tvrtko Ursulin
2015-01-22 14:04 ` Damien Lespiau
2015-01-22 15:28 ` Tvrtko Ursulin
2015-01-22 15:47 ` Damien Lespiau
2015-01-22 15:54 ` Tvrtko Ursulin
2015-01-22 16:07 ` Damien Lespiau
2015-01-23 11:13 ` [RFC v2] " Tvrtko Ursulin
2015-01-23 11:27 ` Chris Wilson
2015-01-23 14:02 ` Tvrtko Ursulin
2015-01-23 15:53 ` Daniel Vetter
2015-01-23 16:49 ` Tvrtko Ursulin
2015-01-24 9:47 ` Daniel Vetter
2015-01-26 11:08 ` Tvrtko Ursulin
2015-01-28 9:20 ` Daniel Vetter
2015-01-23 17:30 ` Chris Wilson
2015-01-24 9:41 ` Daniel Vetter
2015-01-24 16:08 ` Chris Wilson
2015-01-26 7:52 ` Daniel Vetter
2015-01-26 9:08 ` Chris Wilson
2015-01-28 9:22 ` Daniel Vetter
2015-01-28 9:23 ` Chris Wilson
2015-01-28 9:50 ` Daniel Vetter
2015-01-28 10:07 ` Chris Wilson
2015-02-25 20:46 ` Jesse Barnes
2015-02-26 9:13 ` Chris Wilson
2015-01-27 11:29 ` [RFC v3] " Tvrtko Ursulin
2015-01-27 11:40 ` Chris Wilson
2015-01-27 12:13 ` Tvrtko Ursulin
2015-01-27 12:18 ` Chris Wilson
2015-01-27 13:43 ` Tvrtko Ursulin
2015-01-28 9:25 ` Daniel Vetter [this message]
2015-01-28 9:29 ` Daniel Vetter
2015-01-28 16:52 ` Tvrtko Ursulin
2015-01-29 16:14 ` 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=20150128092522.GL4764@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.intel.com \
/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