From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Introduce vblank work function
Date: Fri, 6 Dec 2013 08:49:01 -0800 [thread overview]
Message-ID: <20131206084901.4676db94@jbarnes-desktop> (raw)
In-Reply-To: <20131206134229.GM27344@phenom.ffwll.local>
On Fri, 6 Dec 2013 14:42:29 +0100
Daniel Vetter <daniel@ffwll.ch> wrote:
> On Fri, Dec 06, 2013 at 12:12:21PM +0000, Bloomfield, Jon wrote:
> > Ok thanks.
> >
> > To add weight to it becoming official in some form, we're using it for various deferred operations:
> > drm/i915: Make plane switching asynchronous
> > drm/i915: Asynchronously unpin the old framebuffer after the next vblank
> >
> > They aren't my patches but I believe they should be upstreamed in the near future. The claim is that these give a noticeable performance boost.
> >
> > I'll leave it in and hope it becomes official.
>
> For this stuff the upstream plane is to merge Ville's nuclear pageflip
> code, which is the full deal solution for all these issues. I haven't read
> his latest wip code to see what exactly he's using for all the vblank
> work.
I don't think that should block getting the vblank worker code in along
with the trivial change to the sprite code to avoid a wait_vblank in
the buffer switching case. We've needed that since this code went in,
but for some reason Chris's code has been stalled the whole time (and
didn't we have a wq patch for the sprite unpin even before that?).
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2013-12-06 16:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-04 22:07 RFC asynchronous vblank tasks Chris Wilson
2013-07-04 22:07 ` [PATCH 1/5] drm/i915: Asynchronously unpin the old framebuffer after the next vblank Chris Wilson
2013-07-04 22:07 ` [PATCH 2/5] drm/i915/sprite: Make plane switching asynchronous Chris Wilson
2013-07-04 22:07 ` [PATCH 3/5] drm/i915: Synchronize userspace palette LUT (i.e. gamma) changes to vblank Chris Wilson
2013-07-04 22:07 ` [PATCH 4/5] drm/i915: Up/downclock LVDS on vblanks Chris Wilson
2013-07-04 22:07 ` [PATCH 5/5] drm/i915: Boost DMA qos whilst performing uninterruptible waits for the GPU Chris Wilson
2013-07-05 8:42 ` RFC asynchronous vblank tasks Daniel Vetter
2013-07-05 8:48 ` [PATCH] drm/i915: Introduce vblank work function Chris Wilson
2013-12-06 10:44 ` Bloomfield, Jon
2013-12-06 12:06 ` Daniel Vetter
2013-12-06 12:12 ` Bloomfield, Jon
2013-12-06 13:42 ` Daniel Vetter
2013-12-06 16:49 ` Jesse Barnes [this message]
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=20131206084901.4676db94@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=daniel@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox